Skip to main content
Glama

list_issues

Read-only

Issues as the dashboard lists them, with counts for the environment and range: a tab (unresolved by default), a sort, and q in the search language (statoss.com/docs/search) as Issues reads it: words, /regex/, level:error, category:billing, priority:high, assigned:me, is:unresolved, age:-24h, field:value, with -term or !key:value to leave out, a OR b, key:[a, b], * at either end of a value, key:>500 and has:key. Pages with cursor.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoThe search, as Issues reads it.
tabNounresolved, review, regressed, archived, resolved, or all for every status.
appsNoApps by id or slug, from list_apps; every app the key reaches when left out. appId wins over it.
sortNolast (seen), first (seen), events or users.
appIdNoAn app's id or slug, from list_apps. Holds the call to that app.
limitNoHow many, from 1 to 100. Default 25.
rangeNoHow far back. 14d when left out.
cursorNoThe cursor the last page gave, for the next one.
environmentNoAn environment's name, such as production. Every one when left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / tab / description
      Previous value: -"unresolved, review, regressed, archived or resolved."New value: +"unresolved, review, regressed, archived, resolved, or all for every status."
    • changedInput schema / properties / tab / enum
      Previous value: -[
      -  "unresolved",
      -  "review",
      -  "regressed",
      -  "archived",
      -  "resolved"
      -]New value: +[
      +  "unresolved",
      +  "review",
      +  "regressed",
      +  "archived",
      +  "resolved",
      +  "all"
      +]
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the tab defaults to unresolved, results carry counts for the environment and range, and results are paginated via cursor. It does not describe permissions or result ordering behavior, so it stops 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.

Conciseness3/5

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

Everything present is substantive, but it is delivered as one long run-on sentence with a comma-spliced enumeration of search operators, and the phrase 'as Issues reads it' appears twice (description and schema). The purpose and defaults are front-loaded, yet the operator list would be far more scannable as a short structured block.

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 nine-parameter, no-output-schema listing tool with minimal annotations, the description covers the essentials: what is listed, default tab, range default, counts, and cursor paging, plus a full account of the q grammar. It lacks any statement of what a result record contains (issue id, title, counts placement), which is the main remaining gap given there is no output schema.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description goes beyond it by spelling out the q search language in detail — bare words, /regex/, field:value forms like level:error and assigned:me, negation with -term or !key:value, OR, bracketed lists, wildcards, comparisons, and has:key. That materially enriches the otherwise terse schema entry, though limit, cursor, and appId get nothing beyond their schema text.

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?

The description states the resource and scope clearly: issues as the dashboard lists them, with counts for the environment and range, plus tab/sort/q filtering and cursor pagination. It distinguishes this from get_issue implicitly by being a listing tool, but it never names a sibling or says why an agent would pick this over search_events or list_issue_events.

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?

Usage is implied rather than stated: the mention of a default unresolved tab and the dashboard framing tell the agent this is the standard issue browser, and 'Pages with cursor' signals paging. There is no explicit when-to-use/when-not guidance and no routing to alternatives such as search_events or list_issue_events.

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