Skip to main content
Glama

Search a GitHub repository's issues or pull requests

github_issues
Read-only

Issues or pull requests of a GitHub repository, searched by words and state (open, closed or all), newest updated first: number, title, state, labels, author, comments, dates and link. Related tools on this server, for a different need: github_releases when you need to list a GitHub repository's latest releases; github_repo when you need a public GitHub repository: stars, forks, watchers, open. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoWords to search for (optional)
repoYesowner/name or a github.com URL
typeNoissue (default) or pr
limitNo1 to 30 (default 10)
stateNoopen (default), closed or all

Output Schema

NameRequiredDescriptionDefault
repoNo
itemsNo
queryNo
totalNo
sourceNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With readOnlyHint and openWorldHint already declared, the description still adds real behavior: result ordering (newest updated first), the returned fields, and an explicit cost model of $0.002 per successful call with failed calls uncharged. The payment mechanics (x402/USDC) are useful preconditions an agent must know before calling.

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 core purpose is front-loaded, but the first sentence crams a long return-field enumeration into the same breath as the purpose, and that enumeration is redundant when an output schema exists. The pricing sentence is buried at the end where it is easy to skim past.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only search tool with a rich input schema and an output schema, the description covers purpose, ordering, cost, and alternatives. Only the `type` parameter behavior and any pagination/limit expectations are left unaddressed.

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%, so the baseline is 3. The description restates the state values and word-search intent already documented in the schema, and never clarifies the `type` switch (issue vs pr), the limit range, or accepted repo formats.

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 opening clause gives a specific verb and resource: issues or pull requests of a GitHub repository, searched by words and state, sorted newest-updated-first. It is clearly distinguishable from github_releases and github_repo, which are named explicitly.

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

Usage Guidelines4/5

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

It explicitly routes two adjacent needs away from this tool (github_releases for latest releases, github_repo for repo metadata) with concrete conditions. It does not address the closely related github_search sibling, so the when-not-to-use picture is only partly drawn.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources