Skip to main content
Glama
Sign In
github-mcp

github-mcp

by AbdeeBuilds
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_pull_requests

List pull requests in a GitHub repository. Filter by open, closed, or all states and set the maximum number to return.

Instructions

List pull requests in a GitHub repository.

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

Input Schema

NameRequiredDescriptionDefault
repoYesRepository name
limitNoMaximum number of pull requests to return
ownerYesRepository owner (user or org)
stateNoFilter by pull request stateopen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, and the description only states it lists pull requests. It does not disclose aspects like pagination, rate limiting, authentication needs, or that it is a read-only operation.

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

Conciseness3/5

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

The description is a single sentence, very concise, but it lacks structure and could be more informative without being verbose. It earns its place but does not add value beyond the bare minimum.

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 with 4 parameters and no output schema or annotations, the description is minimal. It does not cover default sorting, pagination behavior, or return format, leaving gaps for the agent.

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 coverage is 100% with parameter descriptions, so the description adds no additional meaning. It does not repeat parameter details, but also does not enhance understanding beyond the schema.

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 verb 'List', the resource 'pull requests', and the location 'GitHub repository'. It distinguishes from sibling tools like 'get_pull_request' which retrieves a single PR.

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?

The description does not provide explicit guidance on when to use this tool versus alternatives such as 'get_pull_request' or 'list_issues'. Usage is implied for listing multiple pull requests, but no exclusions or context are given.

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

Deploy Server

Other Tools