Skip to main content
Glama

list_import_errors

Retrieve import errors from Airflow to identify and resolve DAG loading issues, enabling efficient troubleshooting of deployment problems.

Instructions

[Tool Role]: Lists import errors in Airflow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function that implements the list_import_errors tool by querying the Airflow /importErrors API endpoint with optional pagination parameters.
    async def list_import_errors(limit: int = 20, offset: int = 0) -> Dict[str, Any]:
        """[Tool Role]: Lists import errors in Airflow."""
        params = {'limit': limit, 'offset': offset}
        query_string = "&".join([f"{k}={v}" for k, v in params.items()])
        resp = await airflow_request("GET", f"/importErrors?{query_string}")
        resp.raise_for_status()
        return resp.json()
  • Registers the common tools including list_import_errors for Airflow API v1 by calling register_common_tools after setting the v1-specific airflow_request function.
    common_tools.register_common_tools(mcp)
  • Registers the common tools including list_import_errors for Airflow API v2 by calling register_common_tools after setting the v2-specific airflow_request function.
    common_tools.register_common_tools(mcp)
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 burden of behavioral disclosure. It states the action ('Lists') but lacks details on permissions, rate limits, pagination behavior, or response format. The description doesn't add meaningful context beyond the basic action, leaving gaps for a tool with parameters and output schema.

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 that front-loads the core purpose with no wasted words. It uses a clear '[Tool Role]' prefix for structure, making it immediately scannable and appropriately sized for its simple function.

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?

Given the tool has an output schema (which handles return values) and only 2 simple parameters, the description is minimally complete. However, with no annotations and 0% schema description coverage, it lacks behavioral context and parameter semantics. The description covers the basic purpose but doesn't add enough value beyond what structured fields provide.

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 0%, so the schema provides no parameter descriptions. The tool description doesn't mention parameters at all, failing to compensate for the coverage gap. However, with only 2 parameters (limit and offset) and default values provided in the schema, the baseline is 3 as the schema still offers some structure despite lack of descriptions.

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 clearly states the verb ('Lists') and resource ('import errors in Airflow'), making the purpose immediately understandable. It distinguishes from siblings like 'get_import_error' (singular) and 'all_dag_import_summary' (summary-focused), though it doesn't explicitly mention these distinctions. The description is specific but lacks explicit sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context, or exclusions, nor does it reference sibling tools like 'get_import_error' for single errors or 'all_dag_import_summary' for summaries. Usage is implied only by the tool name and description.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/call518/MCP-Airflow-API'

If you have feedback or need assistance with the MCP directory API, please join our Discord server