github-updates

Overview Schema Source Related Servers Discussions Admin

search_issues

Search a GitHub repository's issues and pull requests using GitHub query filters. Returns total counts and matching items for drafting project updates.

Instructions

Busca issues y pull requests de un repo con la sintaxis de búsqueda de GitHub.

repo: "owner/nombre". query: filtros de GitHub tal cual. Ejemplos: "is:pr is:merged merged:2022-10-01..2022-10-31", "is:issue is:open", "is:issue closed:>=2026-09-20", "label:bug", texto libre. Incluye siempre is:issue o is:pr (GitHub lo exige con tokens fine-grained). No admite repo:/org:/user:, OR/AND/NOT ni paréntesis: haz una búsqueda por cada consulta. limit: máximo de resultados (tope 100). Devuelve total_count (total real en GitHub) e items (como mucho limit).

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": "search_issues"
  }
}

Input Schema

Name	Required	Description	Default
`repo`	Yes
`limit`	No
`query`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations the description carries the full burden and does well: it discloses the required is:issue/is:pr token constraint, the unsupported qualifiers, the limit cap of 100, and the return shape (total_count vs items). It does not state read-only/no-side-effect behavior or rate limits, which keeps it short of a 5.

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?

Purpose is front-loaded, then parameters are described in a compact per-field layout. The query examples are numerous but each illustrates a distinct supported qualifier, so the length is mostly earned.

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 3-param search tool with no output schema and no annotations, the description supplies query syntax, constraints, limits, and even the return structure (total_count, items). An agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, yet the description documents all three parameters: repo format ('owner/nombre'), the full query syntax with examples, and limit ('máximo de resultados, tope 100'). It fully compensates for the empty 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?

States a specific verb ('Busca') and resource ('issues y pull requests de un repo') plus the mechanism (sintaxis de búsqueda de GitHub). It is inherently distinguishable from the sibling get_issue, which fetches a single item, while this searches many.

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?

Gives concrete query examples and explicit exclusions (no repo:/org:/user:, no OR/AND/NOT, no parentheses — run one search per query). It does not explicitly compare against get_issue, but the constraints on how to use it are unusually thorough.

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

Deploy Server