Skip to main content
Glama

list_dags

Read-only

Retrieve Apache Airflow DAGs using filters, pagination, sorting, and regex matching to find and inspect workflows.

Instructions

List DAGs using Airflow 3.3.1 API filters, pagination and sorting.

*_pattern is case-insensitive substring matching; *_prefix_pattern is case-sensitive. Dates use ISO 8601 with timezone. Lists become repeated query parameters. Prefix order_by fields with '-' for descending order. Unset filters use API defaults. dag_id_regex adds Python regex search (inline flags supported), applied before offset/limit. Regex scans at most 1000 native-filtered candidates; limit=0 returns all matches.

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
tagsNo
limitNo
offsetNo
ownersNo
pausedNo
order_byNo
bundle_nameNo
is_favoriteNo
dag_id_regexNo
dag_run_stateNo
exclude_staleNo
bundle_versionNo
dag_id_patternNo
timetable_typeNo
tags_match_modeNo
asset_dependencyNo
has_import_errorsNo
has_asset_scheduleNo
last_dag_run_stateNo
dag_run_end_date_gtNo
dag_run_end_date_ltNo
dag_run_end_date_gteNo
dag_run_end_date_lteNo
dag_id_prefix_patternNo
dag_run_start_date_gtNo
dag_run_start_date_ltNo
dag_run_start_date_gteNo
dag_run_start_date_lteNo
dag_display_name_patternNo
dag_display_name_prefix_patternNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds genuinely new operational behavior: dag_id_regex runs before offset/limit, scans at most 1000 native-filtered candidates, and limit=0 returns all matches. Those limits are the kind of cost/scale disclosure agents cannot get from annotations.

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?

Front-loaded with the action and compressed into five bullet-style sentences with no filler. The terse phrasing ("Lists become repeated query parameters", "Unset filters use API defaults") is dense but each line conveys a distinct rule.

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?

For a 30-parameter read tool with no output schema, the definition covers filter semantics and regex cost but says nothing about the response shape (whether a total count or cursor accompanies the page), and leaves roughly half the filters unexplained. Adequate to invoke, not complete enough to predict results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 30 parameters, so the description carries the burden and does so for the highest-risk ones: the case-sensitivity split between *_pattern and *_prefix_pattern, ISO 8601 dates with timezone, list-to-repeated-parameter conversion, '-' descending prefix on order_by, and dag_id_regex evaluation order. Many parameters (tags_match_mode, exclude_stale, asset_dependency, has_import_errors, bundle_*) remain undocumented, so it is strong but not complete compensation.

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 ("List DAGs") and pins the API surface (Airflow 3.3.1 filters, pagination, sorting). It is unambiguously about the DAG resource versus siblings like list_runs or list_tasks, but it never explicitly distinguishes itself from them.

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 description explains filter mechanics (pattern vs prefix pattern, ISO 8601, repeated query params, '-' for descending) but gives no explicit when-to-use or when-not guidance, and names no alternative. Usage is implied by the filter catalog rather than stated.

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