Skip to main content
Glama
call518

MCP-Airflow-API

by call518
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

list_task_instances_all

List Airflow task instances with comprehensive filters for state, duration, execution dates, pool, DAG, and task ID.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
poolNo
limitNo
stateNo
dag_idNo
offsetNo
task_idNo
dag_run_idNo
duration_gteNo
duration_lteNo
end_date_gteNo
end_date_lteNo
start_date_gteNo
start_date_lteNo
execution_date_gteNo
execution_date_lteNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Removedv3.6.5
  2. 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"
  3. 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"
+}
  4. First observed

TDQS

C2.6/5.0
Behavior2/5

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

No annotations exist, and the description only mentions 'comprehensive filtering options' without detailing behavior such as pagination, limits, or 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?

Single sentence is concise and front-loaded, but overly brief for a tool with 15 parameters.

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?

With 15 parameters, no schema descriptions, no annotations, and a vague description, the tool lacks essential context for correct usage despite having an output schema.

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 description must compensate. It only says 'comprehensive filtering options', offering no insight into parameter meanings or usage beyond names.

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?

Clearly states the tool lists task instances with filtering options, but lacks differentiation from sibling 'list_task_instances_batch'.

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 tool versus alternatives like 'list_task_instances_batch' or other listing tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/call518/MCP-Airflow-API'

If you have feedback or need assistance with the MCP directory API, please join our Discord server