github-review-queue-mcp

Comment on a pull request

comment_on_pull_request

Post a Markdown comment on a pull request's conversation as yourself, so anyone with repository access can see your feedback or reply.

Instructions

Posts a comment on a pull request's conversation, as you. Everyone with access to the repository can see it.

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": {
      "repo": "<repo>",
      "number": "<number>",
      "body": "<body>"
    },
    "name": "comment_on_pull_request"
  }
}

Input Schema

Name	Required	Description
`body`	Yes	Comment text (Markdown)
`repo`	Yes	Repository as "owner/name", for example "octocat/hello-world"
`number`	Yes	Pull request number

Output Schema

Name	Required	Description	Default
`id`	Yes
`url`	Yes
`created_at`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 3, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true. The description adds real context beyond those flags: the comment is attributed "as you" (it uses the caller's identity) and is visible to everyone with repository access, which matters for a public write.

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?

A single front-loaded sentence with no filler; the identity and visibility facts are the two most decision-relevant details and both are present.

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

Completeness4/5

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

An output schema exists, so return values need no explanation, and annotations cover the mutation safety profile. The description covers authorship and audience but omits practical constraints an agent might want, such as whether the comment can be edited or retracted.

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?

Schema description coverage is 100%, with body, repo format, and PR number all documented in the schema itself. The description adds no format, length, or Markdown guidance, so the baseline of 3 applies.

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

Purpose4/5

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

States a specific verb and resource ("Posts a comment on a pull request") and narrows it to the "conversation", which implicitly separates it from submit_pull_request_review. It stops short of naming that sibling explicitly, so an agent must infer the distinction.

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?

There is no when-to-use guidance, no condition that selects this over submit_pull_request_review, and no note about prerequisites such as write access. Usage is only implied by the verb.

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

Deploy Server