GitHub MCP Server

comment_on_pr

Add a comment to a GitHub pull request by specifying owner, repository, PR number, and Markdown-supported text to post feedback or ask questions.

Instructions

Add a comment to a pull request

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "owner": "<owner>",
      "repo": "<repo>",
      "pr_number": "<pr_number>",
      "body": "<body>"
    },
    "name": "comment_on_pr"
  }
}

Input Schema

Name	Required	Description
`body`	Yes	Comment text (supports Markdown)
`repo`	Yes	Repository name
`owner`	Yes	Repository owner (username or org)
`pr_number`	Yes	Pull request number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 13, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits but only states the obvious action. It does not mention side effects, permissions, idempotency, or any side effects beyond adding a comment, which is insufficient for a mutation tool.

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 concise sentence that effectively communicates the core purpose without redundancy. Every word earns its place.

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 the simple action and complete parameter schema, the description lacks behavioral context, usage guidance, and return value information. With no annotations and no output schema, a more complete description is needed to guide the agent effectively.

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

Parameters3/5

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

All parameters are fully documented in the schema (100% coverage), so the description does not need to add parameter details. The description adds no extra meaning, but the schema already provides the necessary semantics, yielding the baseline score.

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 states the action (add) and the resource (comment to a pull request), distinguishing it from sibling tools like get_pr and merge_pr. It is specific and unambiguous.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, context, or exclusions, despite the presence of sibling tools for PR operations.

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

Deploy Server