MCP-Airflow-API

list_task_instances_batch

List Airflow task instances in batch with date and state filters to monitor and troubleshoot workflow executions efficiently.

Instructions

[Tool Role]: Lists task instances in batch with date and state filtering.

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

Input Schema

Name	Required	Description	Default
`limit`	No
`state`	No
`offset`	No
`start_date_gte`	No
`start_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.8/5.0

Behavior2/5

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

No annotations are present, so the description must carry full disclosure. It only states 'Lists task instances in batch with date and state filtering' without explaining what 'batch' entails, pagination behavior, limit/offset semantics, or any side effects. This lacks sufficient detail for an agent to anticipate tool behavior.

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 sentence with a role tag, entirely front-loaded, containing no filler or redundant information. Every word earns its place, achieving excellent conciseness.

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?

Despite having an output schema, the description lacks usage guidance, parameter semantics, and behavioral detail. With 5 parameters and no annotations, this minimal description is insufficient for an agent to confidently invoke the tool, especially given the presence of similar sibling tools.

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%, and the description only vaguely references 'date and state filtering' without explaining limit, offset, or the format of start_date_gte/start_date_lte. It adds minimal meaning beyond the parameter names themselves, failing to compensate for the lack of schema descriptions.

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 uses a specific verb and resource ('Lists task instances') and adds scope ('in batch with date and state filtering'), making the core purpose clear. However, it doesn't explicitly differentiate from the sibling tool list_task_instances_all, so it loses a point for lack of clear sibling distinction.

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 use this tool versus alternatives like list_task_instances_all or get_task_instance_details. No exclusions, prerequisites, or contextual hints are provided, leaving the agent without direction on tool selection.

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

Deploy Server