Skip to main content
Glama
Sign In
MCP-Airflow-API

MCP-Airflow-API

by call518
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_xcom_entries

List XCom entries for a specific task instance using DAG ID, DAG run ID, and task ID, with pagination support.

Instructions

[Tool Role]: Lists XCom entries 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": "list_xcom_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of records to request per page. Default: 20.
dag_idYesExact DAG identifier, as returned by list_dags; not its display name.
offsetNoNumber of records to skip for pagination. Default: 0.
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. Changed5 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 / limit / description
      Added value: +"Maximum number of records to request per page. Default:\n20."
    • addedInput schema / properties / offset / description
      Added value: +"Number of records to skip for pagination. Default: 0."
    • addedInput schema / properties / task_id / description
      Added value: +"Exact task identifier within the selected DAG."
  2. Addedv3.7.2
  3. Removedv3.6.5
  4. Changed6 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 / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / offset / title
      Removed value: -"Offset"
    • removedInput schema / properties / task_id / title
      Removed value: -"Task Id"
  5. First observed

TDQS

C2.8/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 behavioral burden, and it says nothing about pagination (limit/offset exist), whether entries can be empty for unfinished tasks, or whether XCom values are masked/serialized. The existence of an output schema offsets return-value disclosure, but the operational behavior remains undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single clean sentence with no waste and the key scoping fact front-loaded, but its terseness is under-specification rather than effective concision for a 5-parameter paginated tool.

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?

For a tool with 5 params, required identifiers, and paging controls, the description omits pagination behavior and task-state context entirely. An output schema covers return shape, but an agent still lacks guidance on obtaining valid dag_run_id/task_id values.

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%, with each parameter documented including defaults and ID semantics ('as returned by list_dags'), so the baseline of 3 applies. The description adds nothing beyond the schema.

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 XCom entries') plus the scoping unit ('for a specific task instance'), so its role is unambiguous. It doesn't explicitly contrast with the sibling get_xcom_entry (single entry), though the plural 'entries' lets an agent infer the difference.

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 versus get_xcom_entry, or versus listing task instances first. It doesn't mention prerequisites such as needing a completed task run or that results may be paged.

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

Deploy Server

Other Tools