MCP-Airflow-API

list_task_instances_all

List Apache Airflow task instances using filters for DAG, task, state, date, and duration to monitor workflow execution.

Instructions

[Tool Role]: Lists task instances with comprehensive filtering options.

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

Input Schema

Name	Required	Description	Default
`pool`	No
`limit`	No
`state`	No
`dag_id`	No
`offset`	No
`task_id`	No
`dag_run_id`	No
`duration_gte`	No
`duration_lte`	No
`end_date_gte`	No
`end_date_lte`	No
`start_date_gte`	No
`start_date_lte`	No
`execution_date_gte`	No
`execution_date_lte`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Jul 31, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are present, so the description carries full responsibility for behavioral disclosure. It only states that it lists task instances with filters, but does not disclose pagination, sorting, return format, or any side effects.

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?

The description is a single concise sentence with no wasted words, making it easy to read. It is front-loaded with the main action (lists) and object (task instances).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex tool with 15 parameters and no annotations, this one-line description is severely incomplete. It lacks usage context, parameter details, and differentiation from sibling tools, making it insufficient for an agent to select and invoke correctly.

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?

With 15 parameters and 0% schema description coverage, the description must compensate by explaining parameter semantics. It merely says 'comprehensive filtering options,' adding no specific meaning beyond what parameter titles already provide.

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 it lists task instances and mentions comprehensive filtering, which aligns with the tool's name. However, it does not distinguish from the sibling tool list_task_instances_batch, which also lists task instances.

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 explicit guidance is provided on when to use this tool versus alternatives like list_task_instances_batch or get_task_instance_details. The description only implies usage for listing with filters.

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

Deploy Server