Skip to main content
Glama

List error issues

list_error_issues
Read-only

Start here to see what is broken: grouped issues from the backend and the app together, each with its source, level, status, event and user counts. Newest activity first, unresolved only. Console lines from the app are hidden unless include_console is true. Pass next_cursor to read on.

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

Input Schema

NameRequiredDescriptionDefault
sortNoDefault last_seen. new = first seen most recently
levelNo
limitNoRows (default 25)
sinceNoLast seen since: an ISO time, or 30m, 24h, 7d
cursorNonext_cursor from the last answer
sourceNoThe server, the app, or both (default all)
statusNoWhich issues (default unresolved)
releaseNoText in a release the issue was seen in: 2.0.77+185, or package@2.0.77+185
platformNoLike python, ios, android
environmentNoIssues with an event in this environment
include_sparkNoAdd a 14-day sparkline per row (default false)
include_legacyNoAlso list issues grouped before grouping v2 (default false)
include_consoleNoAlso list console lines from the app (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / release / description
      Previous value: -"Text in a release the issue was seen in"New value: +"Text in a release the issue was seen in: 2.0.77+185, or package@2.0.77+185"
  2. Changed12 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "next_cursor from the last answer",
      +  "maxLength": 300,
      +  "type": "string"
      +}
    • addedInput schema / properties / environment
      Added value: +{
      +  "description": "Issues with an event in this environment",
      +  "maxLength": 40,
      +  "type": "string"
      +}
    • addedInput schema / properties / include_console
      Added value: +{
      +  "description": "Also list console lines from the app (default false)",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / include_spark
      Added value: +{
      +  "description": "Add a 14-day sparkline per row (default false)",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / level
      Added value: +{
      +  "enum": [
      +    "fatal",
      +    "error",
      +    "warning",
      +    "info"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Rows (default 25)",
      +  "maximum": 100,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / platform
      Added value: +{
      +  "description": "Like python, ios, android",
      +  "maxLength": 20,
      +  "type": "string"
      +}
    • addedInput schema / properties / release
      Added value: +{
      +  "description": "Text in a release the issue was seen in",
      +  "maxLength": 200,
      +  "type": "string"
      +}
    • addedInput schema / properties / since
      Added value: +{
      +  "description": "Last seen since: an ISO time, or 30m, 24h, 7d",
      +  "maxLength": 40,
      +  "type": "string"
      +}
    • addedInput schema / properties / sort
      Added value: +{
      +  "description": "Default last_seen. new = first seen most recently",
      +  "enum": [
      +    "last_seen",
      +    "events",
      +    "users",
      +    "new"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / source
      Added value: +{
      +  "description": "The server, the app, or both (default all)",
      +  "enum": [
      +    "backend",
      +    "frontend",
      +    "all"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / status / description
      Previous value: -"Which issues to include (default unresolved)"New value: +"Which issues (default unresolved)"
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds real behavior: grouping is unified across backend and app, results are newest-activity-first and unresolved-only by default, console lines are suppressed unless include_console is true, and pagination continues via next_cursor. It does not mention rate limits or what happens with include_legacy beyond the schema, but the addition over annotations is substantive.

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?

Four short sentences, front-loaded with the purpose and the entry-point cue, then defaults, then the caveat, then pagination. Nothing is wasted and the most decision-relevant facts come first.

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 13 optional parameters and no output schema, the description compensates by describing the row shape (source, level, status, event and user counts) and the sentinel defaults a caller must know. Remaining gaps are minor: no hint about how grouped issues relate to search_error_issues results or what an empty result means.

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 92%, so the schema already documents nearly every parameter, including defaults for sort, limit, source, and status. The description restates the console-hiding behavior of include_console and the cursor continuation but adds no format or interaction detail the schema lacks. Baseline 3 applies; note the description says "next_cursor" while the parameter is named cursor, a small naming mismatch the schema property text resolves.

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 and resource: grouped error issues from backend and app together, with the row fields (source, level, status, event and user counts) spelled out. It signals it is the entry point ("Start here") but never names a sibling such as search_error_issues, so differentiation is implied rather than stated.

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?

"Start here to see what is broken" gives a clear context for selecting this tool over narrower lookups, and the defaults (newest first, unresolved only) are stated so the agent knows what it gets without reading the schema. It stops short of explicit when-not guidance or naming an alternative for text search.

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