airflow-mcp-server

airflow-get-task-instances

Retrieve task instances for a specific Airflow DAG run, including state, try number, and duration.

Instructions

List task instances for a specific Airflow DAG run with state, try_number, duration

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>",
      "dagRunId": "<dagRunId>"
    },
    "name": "airflow-get-task-instances"
  }
}

Input Schema

Name	Required	Description
`dagId`	Yes
`dagRunId`	Yes	dag_run_id (e.g. 'scheduled__2026-05-06T00:00:00+00:00')
`extractFields`	No	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.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.4May 28, 2026
Removedv1.0.2May 15, 2026

Changed1 schema field changedv1.0.0May 14, 2026

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

First observedv0.1.0May 7, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It only says 'list', implying a read operation, but does not disclose any behavioral traits such as pagination, permissions, limits, or side effects. Minimal transparency.

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, 14 words, front-loaded with action and resource. Every word earns its place.

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 simple listing tool with no output schema, the description adequately states the core function but lacks details on parameter usage and return format. Could be more complete with examples or constraints.

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

Parameters2/5

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

The description does not explain any input parameters; it only mentions output fields. Of the three parameters (dagId, dagRunId, extractFields), only dagRunId and extractFields have schema descriptions, but dagId has none. The description adds no additional meaning to the parameters.

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?

The description clearly states the tool lists task instances for a specific Airflow DAG run, specifying returned fields (state, try_number, duration). This distinguishes it from sibling tools like airflow-list-runs (which lists runs) and airflow-get-task-logs (which gets logs).

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 description implies when to use the tool (to list task instances) but provides no explicit guidance on when not to use it or alternatives. The sibling list is given but the description doesn't help choose between them.

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

Deploy Server