Skip to main content
Glama
MCP-Airflow-API

MCP-Airflow-API

by call518

get_task_instance_details

Fetches detailed information for a specific Apache Airflow task instance using DAG ID, DAG run ID, and task ID, enabling task status and execution inspection.

Instructions

[Tool Role]: Gets detailed information for a specific task instance.

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": "get_task_instance_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
dag_idYesExact DAG identifier, as returned by list_dags; not its display name.
task_idYesExact task identifier within the selected DAG.
dag_run_idYesExact DAG run identifier for the selected DAG.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.7.4
    • addedInput schema / properties / dag_id / description
      Added value: +"Exact DAG identifier, as returned by list_dags; not its\ndisplay name."
    • addedInput schema / properties / dag_run_id / description
      Added value: +"Exact DAG run identifier for the selected DAG."
    • addedInput schema / properties / task_id / description
      Added value: +"Exact task identifier within the selected DAG."
  2. Addedv3.7.2
  3. Removedv3.6.5
  4. Changed4 schema fields changedv3.6.6
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / dag_id / title
      Removed value: -"Dag Id"
    • removedInput schema / properties / dag_run_id / title
      Removed value: -"Dag Run Id"
    • removedInput schema / properties / task_id / title
      Removed value: -"Task Id"
  5. First observed

TDQS

C2.9/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 the full burden: it doesn't state that this is a read-only operation, what 'details' comprises, whether it errors on missing instances, or authorization requirements. The only signal is the implicit read semantics of 'Gets'.

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?

A single front-loaded sentence with zero filler. It is efficient, though borderline under-specified rather than richly informative.

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?

An output schema exists and the input schema is fully documented, so the missing pieces are modest. Still, for a read tool with no annotations, a sentence on what 'details' covers and how it relates to the logs/extra-links siblings would make it complete.

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 coverage is 100% and each of the three parameters (dag_id, task_id, dag_run_id) has a clear description including the exactness/'as returned by list_dags' caveat. The description adds nothing beyond this, so baseline 3 applies.

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?

States a specific verb ('Gets') and resource ('detailed information for a specific task instance'), which is clearer than a bare restatement of the name. Sibling tools like get_task_instance_logs and get_task_instance_extra_links are implicitly differentiated by the word 'details', but the description never names them explicitly.

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 on when to use this vs. list_task_instances_all, list_task_instances_batch, get_task_instance_logs, or get_task_instance_extra_links. The agent must infer selection from tool names alone.

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