Skip to main content
Glama
MCP-Airflow-API

MCP-Airflow-API

by call518

list_dataset_events

Lists dataset events from Airflow's v1 API to track data lineage, with optional filtering by dataset URI and source DAG plus pagination.

Instructions

[Tool Role]: Lists dataset events for data lineage tracking (v1 API only - v2 uses Assets).

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_dataset_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of records to request per page. Default: 20.
offsetNoNumber of records to skip for pagination. Default: 0.
dataset_uriNoDataset URI, such as s3://bucket/path; API v1 only. Default: None.
source_dag_idNoOptional identifier of the DAG that produced the events. Default: None.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv3.7.4
    • addedInput schema / properties / dataset_uri / description
      Added value: +"Dataset URI, such as s3://bucket/path; API v1 only.\nDefault: None."
    • 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 / source_dag_id / description
      Added value: +"Optional identifier of the DAG that produced the\nevents. Default: None."
  2. Addedv3.7.2
  3. Removedv3.6.5
  4. Changed5 schema fields changedv3.6.6
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / dataset_uri / title
      Removed value: -"Dataset Uri"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / offset / title
      Removed value: -"Offset"
    • removedInput schema / properties / source_dag_id / title
      Removed value: -"Source Dag Id"
  5. Addedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden; it does convey that this is a read/list operation and flags the API-version limitation. It says nothing about permissions, result ordering, or how events are scoped when dataset_uri is omitted.

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

Conciseness5/5

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

A single front-loaded sentence that names the role and appends the version caveat parenthetically. There is no redundant or filler text.

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 all parameters are documented in the schema, so return values and inputs need no explanation here. What is missing is the relationship to the near-identically-named get_dataset_events sibling and any note on default listing behavior when no dataset_uri filter is given.

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%, so each of the four parameters (limit, offset, dataset_uri, source_dag_id) is already documented in the schema, setting the baseline at 3. The description adds nothing about filtering behavior or defaults beyond what the schema states.

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?

The description gives a specific verb ('Lists'), a specific resource ('dataset events'), and a stated purpose ('data lineage tracking'). It is clear what the tool returns, but it does not differentiate itself from the sibling get_dataset_events, whose name suggests overlapping functionality.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The v1-only caveat ('v2 uses Assets') tells the agent when the tool is applicable, which is a real usage constraint. However, there is no guidance on when to choose this over get_dataset_events, list_datasets, or all_dag_event_summary, leaving the agent to infer the boundary.

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