Skip to main content
Glama
saidsef

GitHub PR Issue Analyser

by saidsef
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

add_inline_pr_comment

Add inline review comments to specific lines in GitHub pull requests, delivering contextual feedback directly at the relevant code during review.

Instructions

Adds an inline review comment to a specific line in a file within a PR.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lineYes
pathYes
pr_numberYes
repo_nameYes
repo_ownerYes
comment_bodyYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
bodyYes
authorYes
html_urlYes
created_atYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changedv19.2.0
    • addedOutput schema / properties / author
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / html_url
      Added value: +{
+  "type": "string"
+}
    • removedOutput schema / properties / updated_at
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / user
      Removed value: -{
-  "additionalProperties": true,
-  "type": "object"
-}
    • changedOutput schema / required
      Previous value: -[
-  "id",
-  "body",
-  "user",
-  "created_at",
-  "updated_at"
-]New value: +[
+  "id",
+  "body",
+  "author",
+  "html_url",
+  "created_at"
+]
  2. Addedv14.0.3
  3. Removedv14.0.0
  4. Addedv11.0.1
  5. Removedv10.0.4
  6. Changed16 schema fields changedv10.0.0
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / comment_body / title
      Removed value: -"Comment Body"
    • removedInput schema / properties / line / title
      Removed value: -"Line"
    • removedInput schema / properties / path / title
      Removed value: -"Path"
    • removedInput schema / properties / pr_number / title
      Removed value: -"Pr Number"
    • removedInput schema / properties / repo_name / title
      Removed value: -"Repo Name"
    • removedInput schema / properties / repo_owner / title
      Removed value: -"Repo Owner"
    • removedInput schema / title
      Removed value: -"add_inline_pr_commentArguments"
    • addedOutput schema / properties / body
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / created_at
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / id
      Added value: +{
+  "type": "integer"
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "additionalProperties": true,
-  "title": "Result",
-  "type": "object"
-}
    • addedOutput schema / properties / updated_at
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / user
      Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
    • changedOutput schema / required
      Previous value: -[
-  "result"
-]New value: +[
+  "id",
+  "body",
+  "user",
+  "created_at",
+  "updated_at"
+]
    • removedOutput schema / title
      Removed value: -"add_inline_pr_commentOutput"
  7. Addedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate the tool is not read-only and not destructive; the description adds the specific behavioral detail that it creates an inline comment on a line, but does not disclose side effects like notifications or permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence of 15 words with no unnecessary information, earning its place efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema, the description fails to explain return values or behavior for invalid inputs. For a mutable tool with 6 required parameters and no parameter descriptions, additional context is needed for proper agent usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description provides no additional meaning for any of the 6 parameters. While parameter names like 'line', 'path', and 'comment_body' are somewhat self-explanatory, there is no guidance on format (e.g., markdown for comment_body) or constraints (e.g., valid line numbers).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly specifies the verb 'adds', the resource 'inline review comment', and the context 'to a specific line in a file within a PR', which distinguishes it from the sibling tool 'add_pr_comments' that likely adds general PR comments.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when needing to comment on a specific line in a PR file, but does not explicitly state when to use this tool versus alternatives like 'add_pr_comments' for general comments, nor does it mention prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/saidsef/mcp-github-pr-issue-analyser'

If you have feedback or need assistance with the MCP directory API, please join our Discord server