Skip to main content
Glama
biswasbiplob

mwaa-mcp-server

by biswasbiplob
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

list-mapped-task-instances

Lists all mapped task instances for a dynamically mapped task, revealing map indices and their states to guide log or detail retrieval.

Instructions

List all mapped instances for a dynamically mapped task.

    Returns all mapped task instances for a task that uses Airflow's dynamic
    task mapping (expand()). Each instance includes its map_index, state,
    start/end times, and execution details.

    Use this to discover which map indices exist and their states before
    fetching logs with get-task-logs or details with get-task-instance.

    Args:
        ctx: The MCP context.
        environment_name: Name of the MWAA environment.
        dag_id: The DAG identifier.
        dag_run_id: The DAG run identifier.
        task_id: The mapped task identifier.
        limit: Maximum number of mapped instances to return.
        offset: Number of mapped instances to skip for pagination.
        region: AWS region override.
        profile_name: AWS CLI profile name override.

    Returns:
        CallToolResult with the list of mapped task instances.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of mapped instances to return.
dag_idYesThe DAG ID.
offsetNoNumber of mapped instances to skip for pagination.
regionNoAWS region override.
task_idYesThe mapped task ID.
dag_run_idYesThe DAG run ID.
profile_nameNoAWS CLI profile name override.
environment_nameNoName of the MWAA environment. If omitted and only one environment exists, it is used automatically.

Tool Definition Quality

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses what each returned instance includes (map_index, state, start/end times, execution details) and mentions pagination via limit/offset. It does not explicitly state side-effect-free behavior, but 'List' and 'Returns' imply it. The lack of auth/rate-limit info is not critical for a read operation.

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?

The opening sentence is clear and front-loaded, but the description includes a lengthy Args block that duplicates the schema parameter descriptions. This redundancy makes it longer than necessary. The usage guidance and return details are valuable, but the structure could be tightened.

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?

No output schema exists, so the description must explain return values, which it does (list of instances with fields). It also provides usage context and pagination. Missing failure modes (e.g., what happens if task is not a mapped task) but overall sufficiently complete for a read-only list tool with 8 parameters and no annotations.

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 all 8 parameters are already documented in the schema. The description repeats the same parameter descriptions in an Args block without adding extra meaning (e.g., formats, constraints, relationships). It adds no value beyond 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 the verb 'List', the resource 'all mapped instances for a dynamically mapped task', and the context of Airflow's dynamic task mapping. It distinguishes from siblings like 'list-task-instances' and 'get-task-instance' by focusing on map indices.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use this to discover which map indices exist and their states before fetching logs with get-task-logs or details with get-task-instance.' This names specific alternatives and provides a clear sequencing recommendation.

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