MCP Server for Apache Airflow

list_task_instance_tries

Retrieve execution attempts for a specific Airflow task instance to monitor performance and debug failures. Use DAG ID, DAG run ID, and task ID to query task execution history.

Instructions

List task instance tries by DAG ID, DAG run ID, and task ID

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>",
      "dag_run_id": "<dag_run_id>",
      "task_id": "<task_id>"
    },
    "name": "list_task_instance_tries"
  }
}

Input Schema

Name	Required	Description	Default
`dag_id`	Yes
`dag_run_id`	Yes
`task_id`	Yes
`limit`	No
`offset`	No
`order_by`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.0Jan 2, 2026

TDQS

C2.8/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 implies a read-only list operation but doesn't disclose behavioral traits like pagination (handled by limit/offset), ordering (order_by), error conditions, or output format. For a tool with 6 parameters and no output schema, this is a significant gap in 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?

The description is a single, efficient sentence with zero waste. It's front-loaded with the core action and key identifiers, making it easy to parse. Every word contributes directly to the tool's purpose.

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?

Given the complexity (6 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain the return values, pagination behavior, or how parameters interact. For a list operation with filtering and sorting options, more context is needed to use it effectively.

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?

Schema description coverage is 0%, so the description must compensate. It mentions three required parameters (dag_id, dag_run_id, task_id) but omits the optional ones (limit, offset, order_by) and provides no semantic context for any parameters. This leaves most parameters undocumented and their purposes unclear.

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 clearly states the verb ('List') and resource ('task instance tries'), specifying the key identifiers (DAG ID, DAG run ID, task ID) needed. It distinguishes from siblings like 'list_task_instances' by focusing on 'tries', but doesn't explicitly contrast them. The purpose is specific and actionable.

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?

No guidance is provided on when to use this tool versus alternatives like 'list_task_instances' or 'get_task_instance'. The description only states what it does, not when it's appropriate or what prerequisites exist. This leaves the agent to infer usage from context.

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

Deploy Server