Retrieve open pull requests or issues from a GitHub repo. Filter by user, organization, repository, or involvement, and paginate results to track pending work.
Lists open pull requests or issues.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| issue | No | pr | |
| per_page | No | Number of results per page (1-100) | |
| filtering | No | involves | |
| repo_name | No | ||
| repo_owner | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v14.0.5Input schema / properties / repo_nameAdded value: +{
+ "default": "",
+ "type": "string"
+}v14.0.3v14.0.0v11.0.1v10.0.4v10.0.0Input schema / additionalPropertiesAdded value: +falseInput schema / properties / filtering / enumPrevious value: -[
- "user",
- "owner",
- "involves"
-]New value: +[
+ "user",
+ "org",
+ "repo",
+ "involves"
+]Input schema / properties / filtering / titleRemoved value: -"Filtering"Input schema / properties / issue / titleRemoved value: -"Issue"Input schema / properties / page / titleRemoved value: -"Page"Input schema / properties / per_page / descriptionAdded value: +"Number of results per page (1-100)"Input schema / properties / per_page / maximumRemoved value: -100Input schema / properties / per_page / minimumRemoved value: -1Input schema / properties / per_page / titleRemoved value: -"Per Page"Input schema / properties / repo_owner / titleRemoved value: -"Repo Owner"Input schema / titleRemoved value: -"list_open_issues_prsArguments"Output schema / additionalPropertiesAdded value: +trueOutput schema / propertiesRemoved value: -{
- "result": {
- "additionalProperties": true,
- "title": "Result",
- "type": "object"
- }
-}Output schema / requiredRemoved value: -[
- "result"
-]Output schema / titleRemoved value: -"list_open_issues_prsOutput"v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, indicating a read operation. The description adds no additional behavioral context beyond the basic action, such as pagination behavior or rate limits, failing to leverage the opportunity to add value.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no fluff. It could be more informative while remaining concise, but it is not overly verbose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (6 parameters, many siblings), the description is insufficient. It lacks information about filtering, pagination, and how it differs from detailed sibling tools like get_pr_content, making it hard for an agent to decide without additional context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With only 17% schema description coverage, the description must compensate by explaining parameters. However, it mentions none of the six parameters, leaving their meanings and defaults completely undocumented.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly states 'Lists open pull requests or issues.' This clearly identifies the action (list) and the resource (open PRs/issues), distinguishing it from sibling tools that create, update, or merge PRs/issues.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No usage guidance is provided. The description does not indicate when to use this tool over alternatives like get_pr_content or get_pr_diff, nor does it mention any prerequisites or filtering capabilities.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/saidsef/mcp-github-pr-issue-analyser'
If you have feedback or need assistance with the MCP directory API, please join our Discord server