Skip to main content
Glama

Upstream.codes

List issues

list_issues
Read-only

List a repository's issues, open by default, filtered by labels, assignee, creator or text.

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": {
      "owner": "<owner>",
      "repo": "<repo>"
    },
    "name": "list_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoText to match in titles and bodies.
repoYesRepository slug.
ownerYesNamespace that owns the repository (user or organization handle).
stateNo
cursorNonextCursor from a previous page.
labelsNoComma-separated label names.
creatorNo
perPageNoResults per page (default 30).
assigneeNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine value by disclosing the default state=open behavior, which the schema does not state (the 'state' enum has no default text). It says nothing about paging behavior despite cursor/perPage parameters existing.

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?

One tight sentence with the verb and resource front-loaded and no filler. The trailing 'filtered by' list is efficient, though it drops state even though the default behavior of state is the most operationally important fact in the sentence.

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

Completeness3/5

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

For a 9-parameter paginated listing tool with only sparse annotations and no output schema, the description is minimally adequate: it covers filters and the default state but not pagination or the search_issues boundary. An agent could still call it correctly, but might page incorrectly or pick the wrong sibling for text-centric queries.

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 67%, so the baseline is roughly a 3. The description adds meaning for labels, assignee, creator and text matching (mapping loosely to 'q') and pins down the default for 'state', but cursor, perPage and the semantics of state=all remain entirely undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb + resource: 'List a repository's issues', with scope (repo-scoped) and the filter axes named. It is clearly distinguishable from get_issue, but it does not acknowledge search_issues, whose purpose overlaps with the 'text' filtering this tool advertises.

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

Usage Guidelines3/5

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

'open by default' and 'a repository's issues' imply the repo-scoped listing context, which is useful. However, there is no explicit when-to-use guidance against the sibling search_issues, and the mention of text filtering actually blurs the boundary between the two rather than resolving it.

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