Skip to main content
Glama
call518

MCP-Airflow-API

by call518
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

list_task_instances_batch

Retrieve task instances in batches with filters for date range and state to monitor specific execution periods.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
stateNo
offsetNo
start_date_gteNo
start_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. Changed6 schema fields changedv3.6.6
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / offset / title
      Removed value: -"Offset"
    • 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"
  3. Changed20 schema fields changedv1.0.0
    • removedInput schema / properties / dag_ids
      Removed value: -{
-  "default": null,
-  "items": {
-    "type": "string"
-  },
-  "title": "Dag Ids",
-  "type": "array"
-}
    • removedInput schema / properties / dag_run_ids
      Removed value: -{
-  "default": null,
-  "items": {
-    "type": "string"
-  },
-  "title": "Dag Run Ids",
-  "type": "array"
-}
    • removedInput schema / properties / duration_gte
      Removed value: -{
-  "default": null,
-  "title": "Duration Gte",
-  "type": "number"
-}
    • removedInput schema / properties / duration_lte
      Removed value: -{
-  "default": null,
-  "title": "Duration Lte",
-  "type": "number"
-}
    • removedInput schema / properties / end_date_gte
      Removed value: -{
-  "default": null,
-  "title": "End Date Gte",
-  "type": "string"
-}
    • removedInput schema / properties / end_date_lte
      Removed value: -{
-  "default": null,
-  "title": "End Date Lte",
-  "type": "string"
-}
    • removedInput schema / properties / execution_date_gte
      Removed value: -{
-  "default": null,
-  "title": "Execution Date Gte",
-  "type": "string"
-}
    • removedInput schema / properties / execution_date_lte
      Removed value: -{
-  "default": null,
-  "title": "Execution Date Lte",
-  "type": "string"
-}
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 100,
+  "title": "Limit",
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "title": "Offset",
+  "type": "integer"
+}
    • removedInput schema / properties / pool
      Removed value: -{
-  "default": null,
-  "items": {
-    "type": "string"
-  },
-  "title": "Pool",
-  "type": "array"
-}
    • removedInput schema / properties / queue
      Removed value: -{
-  "default": null,
-  "items": {
-    "type": "string"
-  },
-  "title": "Queue",
-  "type": "array"
-}
    • 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 / items
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / state / type
      Removed value: -"array"
    • removedInput schema / properties / task_ids
      Removed value: -{
-  "default": null,
-  "items": {
-    "type": "string"
-  },
-  "title": "Task Ids",
-  "type": "array"
-}
  4. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so description must convey behavior. It mentions batch listing but omits permissions, rate limits, pagination behavior, or response details. Output schema exists but description adds no transparency.

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, concise and front-loaded with purpose. The '[Tool Role]:' prefix is slightly unnecessary but does not harm brevity.

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?

Given 5 optional parameters, 0% schema coverage, and no annotations, the description is too minimal. Lacks details on pagination, output format, or usage scenarios despite having 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%. Description mentions date and state filtering covering state, start_date_gte, start_date_lte, but omits limit and offset. No format or enum values explained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 in batch with date and state filtering, using specific verb and resource, differentiating from sibling tools like list_task_instances_all.

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_all or get_task_instance_details. Usage context is implied but not explicit.

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