GitHub MCP Server

github_get_pr_comments

Fetch comments on a GitHub pull request by repository and pull number to review feedback and discussion.

Instructions

獲取 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": {
      "repository": "<repository>",
      "pullNumber": "<pullNumber>"
    },
    "name": "github_get_pr_comments"
  }
}

Input Schema

Name	Required	Description
`per_page`	No	每頁顯示數量 (預設 100)
`pullNumber`	Yes	Pull Request 編號
`repository`	Yes	倉庫標識 (格式: owner/repo)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden, and it discloses almost nothing: no mention of pagination behavior, auth requirements, rate limits, or whether review comments and issue-level comments are both returned. 'Get a list' is the only behavior communicated.

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

Conciseness4/5

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

A single short sentence with no filler and the resource front-loaded. It is efficient, though the brevity veers into under-specification rather than tight conciseness.

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?

For a tool embedded among near-identical siblings (github_get_issue_comments, github_create_pr_comment, github_get_pr_files), the description omits the distinguishing context an agent needs. With no annotations and no output schema, it should at minimum clarify scope and pagination expectations.

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%, so the schema already documents repository (owner/repo), pullNumber, and per_page including its default. The description adds no meaning beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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?

The Chinese description states a specific verb+resource: retrieving a Pull Request's comment list. That is clear enough to identify the operation. It does not, however, differentiate itself from the sibling github_get_issue_comments, which is the likeliest confusion given GitHub treats PR comments as a variant of issue comments.

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 indication of when to use this tool versus the many sibling read tools, nor any prerequisites (auth scope, whether a PR must exist). The agent must infer usage entirely from the name.

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