Skip to main content
Glama
MCP-Airflow-API

MCP-Airflow-API

by call518

list_task_instances_all

List Airflow task instances with filters for DAG, task, run, state, pool, date, and duration to monitor or troubleshoot 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

NameRequiredDescriptionDefault
poolNoOptional list of Airflow pool names to filter task instances. Default: None.
limitNoMaximum number of records to request per page. Default: 100.
stateNoOptional list of task states, such as ["failed", "running"]. Default: None.
dag_idNoExact DAG identifier, as returned by list_dags; not its display name. Default: None.
offsetNoNumber of records to skip for pagination. Default: 0.
task_idNoExact task identifier within the selected DAG. Default: None.
dag_run_idNoExact DAG run identifier for the selected DAG. Default: None.
duration_gteNoOptional minimum task duration in seconds. Default: None.
duration_lteNoOptional maximum task duration in seconds. Default: None.
end_date_gteNoOptional inclusive task end time lower bound, in ISO 8601 format. Default: None.
end_date_lteNoOptional inclusive task end time upper bound, in ISO 8601 format. Default: None.
start_date_gteNoOptional inclusive task start time lower bound, in ISO 8601 format. Default: None.
start_date_lteNoOptional inclusive task start time upper bound, in ISO 8601 format. Default: None.
execution_date_gteNoOptional inclusive execution date (v1) or logical date (v2) lower bound, in ISO 8601 format. Default: None.
execution_date_lteNoOptional inclusive execution date (v1) or logical date (v2) upper bound, in ISO 8601 format. Default: None.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.7.6
    • changedInput schema / properties / execution_date_gte / description
      Previous value: -"Optional inclusive task execution time lower\nbound, in ISO 8601 format. Default: None."New value: +"Optional inclusive execution date (v1) or\nlogical date (v2) lower bound, in ISO 8601 format. Default: None."
    • changedInput schema / properties / execution_date_lte / description
      Previous value: -"Optional inclusive task execution time upper\nbound, in ISO 8601 format. Default: None."New value: +"Optional inclusive execution date (v1) or\nlogical date (v2) upper bound, in ISO 8601 format. Default: None."
  2. Changed15 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. Default: None."
    • addedInput schema / properties / dag_run_id / description
      Added value: +"Exact DAG run identifier for the selected DAG.\nDefault: None."
    • addedInput schema / properties / duration_gte / description
      Added value: +"Optional minimum task duration in seconds.\nDefault: None."
    • addedInput schema / properties / duration_lte / description
      Added value: +"Optional maximum task duration in seconds.\nDefault: None."
    • addedInput schema / properties / end_date_gte / description
      Added value: +"Optional inclusive task end time lower bound, in\nISO 8601 format. Default: None."
    • addedInput schema / properties / end_date_lte / description
      Added value: +"Optional inclusive task end time upper bound, in\nISO 8601 format. Default: None."
    • addedInput schema / properties / execution_date_gte / description
      Added value: +"Optional inclusive task execution time lower\nbound, in ISO 8601 format. Default: None."
    • addedInput schema / properties / execution_date_lte / description
      Added value: +"Optional inclusive task execution time upper\nbound, in ISO 8601 format. Default: None."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of records to request per page. Default:\n100."
    • addedInput schema / properties / offset / description
      Added value: +"Number of records to skip for pagination. Default: 0."
    • addedInput schema / properties / pool / description
      Added value: +"Optional list of Airflow pool names to filter task\ninstances. Default: None."
    • addedInput schema / properties / start_date_gte / description
      Added value: +"Optional inclusive task start time lower bound,\nin ISO 8601 format. Default: None."
    • addedInput schema / properties / start_date_lte / description
      Added value: +"Optional inclusive task start time upper bound,\nin ISO 8601 format. Default: None."
    • addedInput schema / properties / state / description
      Added value: +"Optional list of task states, such as [\"failed\",\n\"running\"]. Default: None."
    • addedInput schema / properties / task_id / description
      Added value: +"Exact task identifier within the selected DAG. Default:\nNone."
  3. Addedv3.7.2
  4. Removedv3.6.5
  5. Changed16 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 / duration_gte / title
      Removed value: -"Duration Gte"
    • removedInput schema / properties / duration_lte / title
      Removed value: -"Duration Lte"
    • removedInput schema / properties / end_date_gte / title
      Removed value: -"End Date Gte"
    • removedInput schema / properties / end_date_lte / title
      Removed value: -"End Date Lte"
    • removedInput schema / properties / execution_date_gte / title
      Removed value: -"Execution Date Gte"
    • removedInput schema / properties / execution_date_lte / title
      Removed value: -"Execution Date Lte"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / offset / title
      Removed value: -"Offset"
    • removedInput schema / properties / pool / title
      Removed value: -"Pool"
    • removedInput schema / properties / start_date_gte / title
      Removed value: -"Start Date Gte"
    • removedInput schema / properties / start_date_lte / title
      Removed value: -"Start Date Lte"
    • removedInput schema / properties / state / title
      Removed value: -"State"
    • removedInput schema / properties / task_id / title
      Removed value: -"Task Id"
  6. Changed27 schema fields changedv1.0.0
    • addedInput schema / properties / dag_id / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / dag_id / type
      Removed value: -"string"
    • addedInput schema / properties / dag_run_id / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / dag_run_id / type
      Removed value: -"string"
    • addedInput schema / properties / duration_gte / anyOf
      Added value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / duration_gte / type
      Removed value: -"number"
    • addedInput schema / properties / duration_lte / anyOf
      Added value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / duration_lte / type
      Removed value: -"number"
    • addedInput schema / properties / end_date_gte / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / end_date_gte / type
      Removed value: -"string"
    • addedInput schema / properties / end_date_lte / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / end_date_lte / type
      Removed value: -"string"
    • addedInput schema / properties / execution_date_gte / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / execution_date_gte / type
      Removed value: -"string"
    • addedInput schema / properties / execution_date_lte / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / execution_date_lte / type
      Removed value: -"string"
    • changedInput schema / properties / limit / default
      Previous value: -20New value: +100
    • addedInput schema / properties / pool / anyOf
      Added value: +[
      +  {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / pool / type
      Removed value: -"string"
    • removedInput schema / properties / queue
      Removed value: -{
      -  "default": null,
      -  "title": "Queue",
      -  "type": "string"
      -}
    • addedInput schema / properties / start_date_gte / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / start_date_gte / type
      Removed value: -"string"
    • addedInput schema / properties / start_date_lte / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / start_date_lte / type
      Removed value: -"string"
    • addedInput schema / properties / state / anyOf
      Added value: +[
      +  {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / state / type
      Removed value: -"string"
    • addedInput schema / properties / task_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Task Id"
      +}
  7. 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 supplied, so the description carries the full burden. It says nothing beyond "lists" — no note on default result volume, pagination semantics for limit/offset, ordering, permission requirements, or what happens when filters are omitted on a large Airflow instance.

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 no filler, though it errs toward under-specification rather than tight economy. There is nothing to trim but also little that earns its place.

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?

An output schema exists, so return values need not be explained, but for a 15-parameter read tool with zero annotations the description is far too thin. It never mentions pagination defaults, result caps, or the difference from the batch/detail siblings.

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 description coverage is 100% across all 15 parameters, including format hints like ISO 8601 and units in seconds, so the schema does the heavy lifting. The description adds no parameter meaning of its own, which is the baseline-3 case.

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 and resource: "Lists task instances." However, it offers no differentiation from close siblings like list_task_instances_batch or get_task_instance_details, so an agent still has to guess which entry point fits its case.

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?

The phrase "comprehensive filtering options" hints at broad, filter-driven listing but gives no explicit when-to-use guidance, no exclusions, and no pointer to the batch or detail siblings. The agent must infer the routing decision entirely.

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