github-review-queue-mcp

List changed files

list_pull_request_files

Read-onlyIdempotent

Lists the files a pull request changes, with additions and deletions per file; optionally includes each file's diff for review.

Instructions

Lists the files a pull request changes, with additions and deletions per file. Set include_patch to also get each file's diff (first 3,000 characters per file).

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>"
    },
    "name": "list_pull_request_files"
  }
}

Input Schema

Name	Required	Description
`repo`	Yes	Repository as "owner/name", for example "octocat/hello-world"
`limit`	No	How many files to return (1-100, default 50)
`number`	Yes	Pull request number
`include_patch`	No	Include each file's diff (default false)

Output Schema

Name	Required	Description	Default
`count`	Yes
`files`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 3, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description adds a genuinely useful behavioral fact the annotations cannot carry: patches are truncated to the first 3,000 characters per file. It does not discuss rate limits or pagination semantics, but the truncation caveat is real added value.

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?

Two tight sentences with the core behavior front-loaded and the optional patch detail second. No filler, no redundancy with the schema.

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

Completeness5/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-value documentation is unnecessary, and annotations cover the safety profile. The description supplies what remains missing: what the list contains (files with per-file add/delete counts) and the patch truncation caveat.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description goes beyond the schema by explaining what include_patch actually yields (each file's diff) and the truncation behavior the schema does not mention. It does not clarify 'limit' beyond the schema's own description, so it is not a full 5.

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 description states a specific verb and resource ('Lists the files a pull request changes') and adds the returned detail ('additions and deletions per file'), which is more than the name alone conveys. It does not explicitly distinguish itself from siblings like get_pull_request, but the file-level scope is concrete enough for an agent to select it.

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 explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as get_pull_request for PR metadata. The only conditional advice concerns include_patch, which is parameter usage rather than tool-selection guidance.

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

Deploy Server