github-fetcher

GitHub pull requests

github_prs

Read-onlyIdempotent

List pull requests in a GitHub repository with filters for state, base or head branch, sort field, and direction to review or triage changes.

Instructions

List pull requests with state, base, head, sort, and direction filters.

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

Input Schema

Name	Required	Description
`base`	No	Base branch filter
`head`	No	Head branch filter, owner:branch
`page`	No	Page number, starting at 1
`repo`	Yes	Repository in owner/name form
`sort`	No	Sort field
`fresh`	No	Bypass the local cache
`state`	No	Pull request state, default open
`per_page`	No	Items per page, default 20
`direction`	No	Sort direction

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 1, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds no further behavioral context such as whether results are cached (the 'fresh' param hints at caching but the schema explains it) or what pagination metadata is returned, so it stays at the annotated baseline.

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 front-loaded sentence with no filler, correctly leading with the verb and resource before the filter list. It is tight, though the filter enumeration is partly redundant with the schema and could have been replaced with a note on caching or result shape.

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?

For a flat, single-required-parameter list tool with full schema coverage, strong read-only annotations, and no output schema, the description plus structured fields give an agent everything needed to invoke it correctly. Nothing essential is missing.

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% — every parameter including repo format, head owner:branch syntax, state defaults, and per_page defaults is documented in the schema. The description only restates a subset of the parameter names (state, base, head, sort, direction) without adding format or semantics beyond the schema, so baseline 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 ('List pull requests') and enumerates the filterable dimensions, so the operation is unambiguous. It does not, however, contrast itself with the sibling github_pr (single PR) or github_search_issues, leaving sibling disambiguation to the tool name alone.

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?

Usage is implied by the filter enumeration — an agent can infer this is for browsing a repo's PRs — but there is no explicit when-to-use, no exclusion of alternatives like github_pr, and no note on prerequisites such as auth or repo access.

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