Skip to main content
Glama

List runner jobs

list_runner_jobs
Read-only

Jobs that ran or wait on FFxF runners, most recent first: repository, workflow and job, label, status (queued with waiting_reason credit, budget or account; running; succeeded; failed, stopped_for_credit when the credit ran out; cancelled; refused with refusal), times, billed minutes and amount, link to the run. Scope: billing.read.

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

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 25.
cursorNometa.next_cursor of the previous page.
statusNoKeep only jobs in this status.
repositoryNoowner/name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / status / description
      Added value: +"Keep only jobs in this status."
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the read-only and open-world profile, but the description adds real value beyond them: sort order, the exact fields returned, the full status taxonomy with sub-states (queued with waiting_reason, stopped_for_credit, refused with refusal), and the required billing.read scope. It stops short of describing pagination behavior, which the schema carries instead.

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?

One dense sentence, front-loaded with the resource and ordering, then the returned fields and the permission scope. It is compact and wastes no words, though the comma-chained field enumeration is harder to scan than a short structured list would be.

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 no output schema, the description carries the return-value burden and does so by enumerating the returned fields, including billed minutes and amount and the run link. Combined with the schema-handled limit/cursor/repository/status parameters and the stated permission scope, an agent has what it needs to call this correctly.

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 earns an extra point because it explains the status values that the enum lists only as bare tokens, including the waiting_reason sub-categories and the distinction between failed, stopped_for_credit, and refused that a filter caller would need to choose correctly.

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 names the resource precisely ('Jobs that ran or wait on FFxF runners') and the ordering ('most recent first'), which is enough to distinguish it from the infrastructure-oriented list_* siblings. The verb 'list' is only implied by the name rather than the text, but the scope is unmistakable.

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 explicit when-to-use statement, no exclusions, and no alternatives named. A reader must infer from the resource that this is the tool for inspecting runner job history; nothing in the text confirms or rules out other paths.

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.