Skip to main content
Glama

list_runs

Read-only

Retrieve existing runs for a specified Airflow DAG, with optional limit and offset for pagination; does not create new runs.

Instructions

List existing runs; never creates runs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dag_id": "<dag_id>"
    },
    "name": "list_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
dag_idYes
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so "never creates runs" largely restates what the annotations say. The description adds nothing new about pagination behavior, default page size (limit=50), ordering, or what a returned run record 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?

Two short clauses, front-loaded with the core action and free of padding. Its brevity is efficient, though the space saved is not spent on anything the agent actually needs.

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 paginated listing tool with three undocumented parameters and no output schema, the definition should say that dag_id is required and how limit/offset paginate. Neither is covered, so an agent must guess at paging semantics.

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

Parameters1/5

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

Schema description coverage is 0% across all three parameters, and the description mentions none of them — not the required dag_id, nor limit/offset or their defaults. The description carries no parameter meaning at all, leaving the agent entirely dependent on bare parameter names.

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?

"List existing runs" states a specific verb and resource, so the agent knows exactly what operation this is. It does not differentiate from the closer siblings such as inspect_run, and its second clause targets a nonexistent create-run alternative rather than a real neighbor.

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 guidance on when to choose this over inspect_run or other list_* siblings, nor any note about paging through results. The only guidance offered is a negative ("never creates runs") that addresses a tool which is not in the sibling set.

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