Skip to main content
Glama

list_issues

List review issues reported against a specific mock endpoint or rule target. Provide either 'targetSlugId' (to filter issues for one specific MOCK-xxxxxx or RULE-xxxxxx badge) or 'mockId' (to retrieve all issues across the mock and all of its rules). Returns an array of issue objects including issue slugId (e.g. 'ISS-xxxxxx'), title, description, status ('OPEN' or 'RESOLVED'), and targetSlugId.

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
mockIdNoOptional database ID of the mock endpoint — returns all issues across the mock's default response and all of its rules. Provide either mockId or targetSlugId.
targetSlugIdNoOptional slug ID of the target Mock or Rule (e.g. 'MOCK-xxxxxx' or 'RULE-xxxxxx'). Provide either targetSlugId or mockId.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / mockId / description
      Previous value: -"Database ID of the mock endpoint — returns all issues across the mock and its rules"New value: +"Optional database ID of the mock endpoint — returns all issues across the mock's default response and all of its rules. Provide either mockId or targetSlugId."
    • changedInput schema / properties / targetSlugId / description
      Previous value: -"The slug ID of the Mock or Rule (e.g. 'MOCK-xxxxxx' or 'RULE-xxxxxx')"New value: +"Optional slug ID of the target Mock or Rule (e.g. 'MOCK-xxxxxx' or 'RULE-xxxxxx'). Provide either targetSlugId or mockId."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the return payload (issue objects with slugId, title, description, status, targetSlugId) and the status enum values. It omits ordering, pagination/limits, and whether the listing includes resolved issues by default, which are the remaining behavioral gaps.

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?

Three tight sentences: purpose first, parameter routing second, return shape third. No filler and nothing repeated from the title.

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?

There is no output schema, and the description compensates by enumerating the returned fields and status values. Combined with full schema coverage on both optional parameters, an agent has enough to call it correctly; only pagination and default filtering behavior are unstated.

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 description coverage is 100%, so both parameters are already documented in the input schema, including the either/or constraint. The description restates the mockId-vs-targetSlugId scope distinction without adding format or edge-case detail beyond the schema, so the baseline of 3 applies.

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 uses a specific verb and resource ('List review issues reported against a specific mock endpoint or rule target') and clarifies the two scoping modes. It does not name the closely related siblings (list_open_issues_for_mock, get_issue), so an agent must infer the difference from the filtering language alone.

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?

It gives clear guidance on the two invocation modes: targetSlugId for a single MOCK-/RULE- badge versus mockId for the whole mock including all rules. It stops short of stating exclusions versus alternatives like list_open_issues_for_mock or get_issue, so the when-not guidance is implicit.

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