Skip to main content
Glama

list_runs

Retrieve paginated job run history, filtered by job, machine, or status, to review past executions and outcomes. Use the cursor to page through results.

Instructions

List job run history, optionally filtered by job, machine, or status. Paginated via 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_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo
job_idNo
statusNo
machine_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses cursor-based pagination, but does not say whether the operation is read-only, what the default page size or ordering is, how far back history is retained, or whether the status filter accepts multiple values.

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?

Two short sentences, front-loaded with the core action, then the optional filters, then pagination. No filler or redundant restatement of the tool name.

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?

With no annotations, no output schema, and zero schema description coverage across five parameters, the description should do more — at minimum default page size, ordering, and return shape. What is present is accurate but leaves meaningful gaps for an agent to guess at.

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 0%, so the description must compensate for five parameters. It adds meaning for job_id, machine_id, status, and cursor, but says nothing about limit (its 1-200 range or default) or the concrete status values, leaving two of five parameters explained only by bare schema types.

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?

States a specific verb and resource ("List job run history") and names the filterable dimensions, which distinguishes it from list_jobs and list_machines in the sibling set. It stops short of explicitly contrasting with those siblings, but the resource is unambiguous.

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?

The phrase "optionally filtered by job, machine, or status" implies when to apply filters, but there is no explicit when-to-use guidance, no exclusions, and no mention of list_jobs as the place to look for job definitions rather than run history. Usage is inferred rather than directed.

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