Skip to main content
Glama
MCP-Airflow-API

MCP-Airflow-API

by call518

list_datasets

Lists datasets in an Airflow v1 system with pagination and optional URI pattern filtering, so you can inspect dataset records for monitoring and management.

Instructions

[Tool Role]: Lists all datasets in the Airflow system (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_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of records to request per page. Default: 20.
offsetNoNumber of records to skip for pagination. Default: 0.
uri_patternNoOptional dataset URI pattern passed to the API (v1 only). Default: None.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.7.4
    • 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 / uri_pattern / description
      Added value: +"Optional dataset URI pattern passed to the API (v1\nonly). Default: None."
  2. Addedv3.7.2
  3. Removedv3.6.5
  4. Changed4 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 / uri_pattern / title
      Removed value: -"Uri Pattern"
  5. Addedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one meaningful trait: this only works against the v1 dataset API (v2 assets are not covered). It says nothing about read-only safety, whether results are paginated by default, or ordering — traits an agent would want before calling a list endpoint, though the limit/offset params hint at paging.

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 the key constraint in parentheses; nothing is padded. The '[Tool Role]:' prefix is slightly redundant boilerplate but costs little.

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 three parameters are documented, so the essentials are covered. The remaining gap is that the version caveat is stated but not resolved — an agent is told v2 uses Assets yet not told what to call instead, which is the one thing it might still need.

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 limit, offset and uri_pattern each fully documented including defaults, so the schema does the work and baseline 3 applies. The description adds no extra semantics such as pattern syntax or matching behavior beyond what the schema already says.

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 all datasets in the Airflow system'), which clearly distinguishes it from get_dataset and list_dataset_events among the siblings. It stops short of naming a sibling or defining scope (e.g. whether all datasets or only those with events/URIs are returned), so it is clear but not fully differentiated.

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?

Usage is only implied by the verb 'lists' — an agent can infer this is the enumeration entry point before calling get_dataset. The parenthetical '(v1 API only - v2 uses Assets)' gives a useful environmental condition for when the tool applies, but there is no explicit when-not guidance or pointer to the sibling that replaces it on v2.

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