Skip to main content
Glama
biswasbiplob

mwaa-mcp-server

by biswasbiplob

list-dag-runs

List DAG runs for a specific DAG, showing execution dates, states, and run IDs. Filter by state or date range, sort, and paginate results for efficient monitoring.

Instructions

List DAG runs for a specific DAG.

    Returns a list of DAG runs with their execution dates, states, and run IDs.
    Results are sorted by execution date descending (newest first) by default.

    Args:
        ctx: The MCP context.
        environment_name: Name of the MWAA environment.
        dag_id: The DAG identifier.
        limit: Maximum number of results.
        offset: Pagination offset.
        state: Filter by run state.
        order_by: Sort order (default: "-execution_date", newest first).
        execution_date_gte: Filter runs on or after this date (ISO 8601).
        execution_date_lte: Filter runs on or before this date (ISO 8601).
        region: AWS region override.
        profile_name: AWS CLI profile name override.

    Returns:
        CallToolResult with the list of DAG runs.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of DAG runs to return.
stateNoFilter by run state (e.g., "success", "failed", "running").
dag_idYesThe DAG ID to list runs for.
offsetNoNumber of DAG runs to skip for pagination.
regionNoAWS region override.
order_byNoSort order for results. Prefix with "-" for descending. Default: "-execution_date" (newest first). Examples: "execution_date", "-start_date", "-end_date".-execution_date
profile_nameNoAWS CLI profile name override.
environment_nameNoName of the MWAA environment. If omitted and only one environment exists, it is used automatically.
execution_date_gteNoFilter runs with execution date >= this value (ISO 8601, e.g., "2026-02-20T00:00:00+00:00").
execution_date_lteNoFilter runs with execution date <= this value (ISO 8601, e.g., "2026-02-21T00:00:00+00:00").
Behavior3/5

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

Without annotations, the description carries the full burden. It discloses that results are sorted descending by default, includes pagination and filtering parameters, and returns execution dates, states, and run IDs. However, it does not mention permissions, error conditions, or whether the operation is inherently read-only, which would be useful behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is overly long due to a full Args block that largely duplicates the input schema. The opening two sentences are useful, but the extensive parameter list adds little value and makes the description bloated. For an MCP tool, the schema already documents parameters, so this structure is inefficient.

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 10 parameters and no output schema, the description covers key aspects: what is returned, default sorting, filtering, pagination, and AWS region/profile overrides. However, it lacks details on output structure beyond a vague 'CallToolResult', potential errors, or edge cases. It is complete enough for basic use but not exhaustive.

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 coverage is 100%, so the baseline is 3. The description repeats much of the schema in its Args list (redundant) but does add some context, such as the default order_by behavior and that results include execution dates, states, and run IDs. This adds marginal value over the schema.

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

Purpose5/5

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

The description clearly states 'List DAG runs for a specific DAG', identifying the verb, resource, and scope. It distinguishes itself from sibling tools like get-dag-run (singular run) and list-task-instances by focusing on DAG runs with details on returned fields.

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 implies when to use the tool (listing runs for a specific DAG with optional filters) but does not explicitly compare to alternatives or state when not to use it. It gives a clear context for usage, but lacks exclusionary guidance or named sibling alternatives.

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/biswasbiplob/mwaa-mcp-server'

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