Skip to main content
Glama

list_jobs

Read-onlyIdempotent

Retrieve pipeline job runs, optionally filter by status, and page through results with a cursor and configurable limit.

Instructions

List pipeline job runs, optionally filtered by status. Paginated.

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

Input Schema

NameRequiredDescriptionDefault
limitNoPage size (1-100).
cursorNoOpaque cursor from a previous page's next_cursor.
statusNo
workspaceNoNamed workspace. Omit to use the default workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds only 'Paginated', which is real behavioral context for a list tool. It does not disclose ordering, default page size, or that results span the selected workspace, leaving the addition thin against a rich annotation set.

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?

Two short sentences with the core purpose front-loaded and zero filler; the 'Paginated.' fragment is efficient. It is arguably terse to the point of under-specification, but no sentence is wasted.

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?

For a four-parameter, zero-required, read-only list tool with strong annotations and no output schema, the description covers purpose and pagination adequately. It omits ordering of results, what a job run record contains, and how the workspace parameter scopes the listing, which an agent would otherwise have to guess.

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 75%, so the schema carries most parameter meaning, including the limit range, the opaque cursor contract, and the workspace default. The description echoes only the status filter ('optionally filtered by status') and adds nothing about limit, cursor, or workspace, so baseline 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?

States a specific verb and resource: 'List pipeline job runs'. The resource is precise enough to separate it from sibling list tools (list_clusters, list_models, list_tables) and from the singular get_job. It stops short of explicitly contrasting with those siblings, so it is clear but not fully differentiated.

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?

'Optionally filtered by status' implies the common usage pattern, but there is no explicit when-to-use guidance, no mention of when to prefer get_job for a single run, and no statement of prerequisites such as workspace context. Usage is inferable but not taught.

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