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

MCP-Airflow-API

by call518
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_event_logs

Retrieve and paginate Apache Airflow event logs, optionally filtered by DAG ID, to monitor cluster activity and audit DAG or task events.

Instructions

[Tool Role]: Lists event logs from Airflow.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of records to request per page. Default: 20.
dag_idNoExact DAG identifier, as returned by list_dags; not its display name. Default: None.
offsetNoNumber of records to skip for pagination. Default: 0.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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. Default: 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."
  2. Addedv3.7.2
  3. Removedv3.6.5
  4. Changed4 schema fields changedv3.6.6
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / dag_id / title
      Removed value: -"Dag Id"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / offset / title
      Removed value: -"Offset"
  5. Changed4 schema fields changedv1.0.0
    • addedInput schema / properties / dag_id / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / dag_id / type
      Removed value: -"string"
    • removedInput schema / properties / run_id
      Removed value: -{
-  "default": null,
-  "title": "Run Id",
-  "type": "string"
-}
    • removedInput schema / properties / task_id
      Removed value: -{
-  "default": null,
-  "title": "Task Id",
-  "type": "string"
-}
  6. First observed

TDQS

C2.3/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, yet it only implies a safe read operation via the verb "Lists". It says nothing about required permissions, result size, ordering, or whether the paginated scan is expensive — all relevant for a log-listing endpoint.

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?

It is a single short sentence with no filler and the purpose is front-loaded, but the brevity reflects under-specification rather than efficient packing of useful information. The '[Tool Role]:' prefix is boilerplate that consumes space without adding meaning.

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?

An output schema exists, so return values needn't be explained, and all three parameters are documented in the schema. However, with zero annotations and many closely related siblings (get_event_log, all_dag_event_summary, list_dag_events), the definition leaves the agent without enough context to choose this tool confidently.

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 limit/offset pagination semantics and the dag_id 'exact DAG identifier, not its display name' caveat are already fully documented in the schema. The description adds nothing beyond it, which is acceptable at baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence "Lists event logs from Airflow" is essentially a restatement of the tool name list_event_logs plus the product name. It gives a verb and resource but adds no scope information (what an event log contains, which events) and does not distinguish it from the sibling get_event_log or all_dag_event_summary.

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?

There is no when-to-use guidance at all — nothing says when to list logs versus calling get_event_log for a single record or all_dag_event_summary for aggregates. The agent must infer the routing decision entirely from tool names.

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