Skip to main content
Glama
Sign In
airflow-mcp-server

airflow-mcp-server

by us-all
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

airflow-list-runs

Retrieve recent runs of an Airflow DAG, optionally filtered by state, with results ordered newest first.

Instructions

List recent runs of one Airflow DAG, optionally filtered by state, ordered newest first

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": {
      "dagId": "<dagId>"
    },
    "name": "airflow-list-runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
dagIdYesAirflow DAG id
stateNoFilter by state (success | running | failed | queued | up_for_retry | ...)
limitNo
extractFieldsNoComma-separated dotted paths to project from response (e.g. 'id,name,owner.name,columns.*.name'). Use `*` as wildcard for arrays/objects. Wrap field names with dots in backticks. Reduces response tokens dramatically on large entities.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.4
  2. Removedv1.0.2
  3. Changed1 schema field changedv1.0.0
    • addedInput schema / properties / extractFields
      Added value: +{
+  "description": "Comma-separated dotted paths to project from response (e.g. 'id,name,owner.name,columns.*.name'). Use `*` as wildcard for arrays/objects. Wrap field names with dots in backticks. Reduces response tokens dramatically on large entities.",
+  "type": "string"
+}
  4. Changed1 schema field changedv0.2.0
    • changedInput schema / properties / state / description
      Previous value: -"Filter by state (success | running | failed | queued | ...)"New value: +"Filter by state (success | running | failed | queued | up_for_retry | ...)"
  5. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses that it lists runs, filters by state, and orders newest first, but lacks details on auth needs, rate limits, or behavior when no runs exist. Adequate but not thorough.

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?

Single sentence that conveys key information efficiently with no wasted words. Front-loaded with action and resource.

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?

For a list tool with 4 parameters and no output schema, the description covers basic functionality. Lacks details on return format, pagination, and error scenarios. Could be more complete but is sufficient for a straightforward list operation.

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 75%, so baseline is 3. Description adds ordering context ('ordered newest first') but otherwise does not elaborate beyond schema. The 'limit' parameter lacks full description in both schema and description.

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

Purpose5/5

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

Clearly states verb 'list', resource 'runs of one Airflow DAG', and specifies optional filter by state and ordering. Differentiates from siblings by specifying one DAG and ordering.

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?

Implies usage for listing DAG runs but does not provide explicit guidance on when to use this tool vs siblings like airflow-get-task-instances or search-tools. No exclusions or alternatives mentioned.

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

Deploy Server

Other Tools