GitHub PR Issue Analyser

Overview Schema Source Related Servers Discussions Admin

Github List Open Issues Prs

github_list_open_issues_prs

Read-only

List open pull requests or issues by user, organization, or repository on GitHub to track active work and review what needs attention.

Instructions

Lists open pull requests or issues. The search is fixed to is:open, so closed and merged items are out of reach here. Call github_search_issues_prs for those, and for any qualifier this tool does not expose.

Workflow and conventions: github_get_skill('issue-management').

Input Schema

Name	Required	Description	Default
`page`	No	Which page of results to return, counting from 1
`issue`	No	pr for pull requests, issue for issues	pr
`per_page`	No	Number of results per page (1-100)
`filtering`	No	involves for items that user authored, is assigned, is mentioned in or commented on, anywhere on GitHub. user for items in that user's repositories. org for an organisation's. repo for one repository	involves
`repo_name`	No	Repository name. Required when filtering is repo, ignored otherwise
`repo_owner`	Yes	Username under involves and user, organisation under org, repository owner under repo

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv46.0.8Oct 15, 2026

changedInput schema / properties / filtering / description

Previous value: -"involves for items that user authored, is assigned, is mentioned in or reviewed, anywhere on GitHub. user for items in that user's repositories. org for an organisation's. repo for one repository"New value: +"involves for items that user authored, is assigned, is mentioned in or commented on, anywhere on GitHub. user for items in that user's repositories. org for an organisation's. repo for one repository"

Addedv42.0.0Sep 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint=false and destructiveHint=false, so safety is largely covered. The description adds the crucial behavioral constraint that the query is hard-pinned to is:open, which is non-obvious from the schema and prevents wasted calls.

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?

Front-loads the core behavior and the limitation, then the alternative, with no filler sentences. The trailing pointer to github_get_skill is terse but adds navigational value rather than noise.

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?

Scope, exclusions, alternative tool, and safety profile are all covered, and an output schema exists so return values need no explanation. Nothing an agent needs in order to call this correctly 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% and the enum values (pr/issue, filtering modes) are fully documented in the schema itself. The description adds no parameter-level syntax, defaults, or interaction details, so the baseline 3 applies.

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?

States a specific verb and resource ("Lists open pull requests or issues") and immediately names the sibling that handles everything else. An agent can distinguish it from github_search_issues_prs without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the fixed scope (is:open), the exclusion (closed and merged items are out of reach), and the exact alternative (github_search_issues_prs) for both those items and any unsupported qualifier. It also routes the agent to github_get_skill for workflow conventions.

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

Deploy Server