Skip to main content
Glama

list_runs

Recover task IDs across chats and retrieve run history with bounded pagination, using limit and offset controls to locate prior work.

Instructions

Recover task IDs across chats, with bounded pagination.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
project_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only hints that results are paginated in a bounded way. It says nothing about ordering, permissions/scope of 'chats', whether results are scoped by project, rate limits, or what the response contains.

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?

A single short sentence with no filler, and the scope qualifier ('across chats') plus the pagination note are packed efficiently. Its brevity is clean, though it edges toward under-specification rather than demonstrating disciplined compression.

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

Completeness2/5

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

For a three-parameter listing tool with no annotations and no output schema, the description omits filtering behavior, pagination mechanics, and return shape. The agent knows only the vaguest outline of what it will get back.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters (limit, offset, project_id), and the description compensates only weakly via the phrase 'bounded pagination'. It never explains that limit/offset control paging, what the defaults mean, or that project_id filters the listing — the one genuinely ambiguous parameter is left entirely undocumented.

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

Purpose3/5

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

The description says it recovers task IDs 'across chats', which gestures at a list operation, but the verb/resource pairing does not match the tool name list_runs and never states plainly that it lists runs (or what a 'run' is). An agent cannot confidently distinguish it from siblings like get_run, read_events, or list_projects based on this text alone.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no mention of any alternative tool. The agent is left to infer that this is the enumeration entry point while get_run retrieves individual runs.

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