Skip to main content
Glama

list_open_issues

Read-only

Lists currently open issues for one repository, newest first, with optional label filtering and exact open-issue counts; pull requests are excluded.

Instructions

List the currently OPEN issues of ONE repository, newest first, optionally filtered by a single label, with the exact total of open issues. Pull requests are excluded. Use for 'what is open', 'how many open issues', or 'open bugs in X'. Do NOT use for closed issues, keyword search, or issues across all repos (use search_issues), or for pull requests (use list_pull_requests).

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

Input Schema

NameRequiredDescriptionDefault
repoYesRepository as 'owner/name' (e.g. 'octocat/hello-world'). A bare name like 'hello-world' is resolved against the authenticated user's account.
labelNoOnly return issues that have this exact label name, e.g. 'bug'. Omit for all open issues.
limitNoMaximum number of items to return (1-50). Totals are reported separately, so a small limit is fine when only a count is needed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing result ordering (newest first), that pull requests are filtered out, and that an exact total is returned separately from the limited item list. It does not mention pagination beyond the limit parameter or any rate-limit behavior, so it stops short of full behavioral disclosure.

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

Conciseness5/5

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

Two sentences, both front-loaded with the identifying fact first (open issues of one repo) and routing guidance second. The trigger phrases and exclusions are compressed with no filler.

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?

With no output schema, the description still conveys the shape of the answer (ordered item list plus an exact total), which is what an agent needs to decide whether a small limit suffices. It does not describe what fields each returned issue carries, leaving a minor gap for follow-up planning.

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%, so the schema already documents repo format, label exact-match, and the limit range. The description only contributes the constraint that filtering is by a SINGLE label, which is a small addition; 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 (list open issues) plus hard scope boundaries: one repository, newest first, single optional label, exact total, pull requests excluded. An agent can distinguish it from search_issues and list_pull_requests 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 gives when-to-use triggers ('what is open', 'how many open issues', 'open bugs in X') and when-not-to-use conditions (closed issues, keyword search, cross-repo, pull requests), naming the correct alternative tool for two of those exclusions.

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