Skip to main content
Glama
MCP-Airflow-API

MCP-Airflow-API

by call518

list_dags

Lists all DAGs registered in an Airflow cluster with pagination and filters by DAG ID or display name, helping you find and inspect workflows.

Instructions

[Tool Role]: Lists all DAGs registered in the Airflow cluster with pagination support.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of DAGs to return (default: 20)
offsetNoNumber of DAGs to skip for pagination (default: 0)
fetch_allNoIf True, fetches all DAGs regardless of limit/offset
id_containsNoFilter DAGs by ID containing this string
name_containsNoFilter DAGs by display name containing this string

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv3.7.4
    • addedInput schema / properties / fetch_all / description
      Added value: +"If True, fetches all DAGs regardless of limit/offset"
    • addedInput schema / properties / id_contains / description
      Added value: +"Filter DAGs by ID containing this string"
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of DAGs to return (default: 20)"
    • addedInput schema / properties / name_contains / description
      Added value: +"Filter DAGs by display name containing this string"
    • addedInput schema / properties / offset / description
      Added value: +"Number of DAGs to skip for pagination (default: 0)"
  2. Addedv3.7.2
  3. Removedv3.6.5
  4. Changed6 schema fields changedv3.6.6
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / fetch_all / title
      Removed value: -"Fetch All"
    • removedInput schema / properties / id_contains / title
      Removed value: -"Id Contains"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / name_contains / title
      Removed value: -"Name Contains"
    • removedInput schema / properties / offset / title
      Removed value: -"Offset"
  5. First observed

TDQS

B3.4/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 full behavioral burden. It discloses that the operation lists registered DAGs and supports pagination, and listing implies a safe read operation. However, it does not mention permissions, rate limits, or whether the listing is live versus cached.

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?

The description is a single efficient sentence with no wasted words. The tool role and core behavior are front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list operation with full schema coverage and an output schema, the description is mostly complete: it states the resource, scope, and pagination behavior. The main gap is sibling differentiation, which is a usage-guidance concern rather than a missing core detail.

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 the input schema already documents all five parameters clearly. The description only adds 'pagination support,' which is already covered by the limit/offset/fetch_all parameters, so it does not add meaningful semantic detail 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?

The description names a specific verb and resource: 'Lists all DAGs registered in the Airflow cluster.' It also mentions pagination support, which clarifies scope. It does not explicitly differentiate this tool from siblings like running_dags, failed_dags, or get_dags_detailed_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?

The description implies the tool is for enumerating DAGs but gives no explicit when-to-use guidance. It does not mention when to prefer this over running_dags, failed_dags, get_dag, or get_dags_detailed_batch.

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