Skip to main content
Glama
nikhil-ganage

MCP Server Airflow Token

update_dag_run_state

Modify the execution status of an Airflow DAG run to manage workflow progression or resolve issues.

Instructions

Update a DAG run state by DAG ID and DAG run ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dag_idYes
dag_run_idYes
stateNo

Implementation Reference

  • The async handler function that implements the core logic of the 'update_dag_run_state' tool by calling the Airflow DAGRunApi to update the state.
    async def update_dag_run_state(
        dag_id: str, dag_run_id: str, state: Optional[str] = None
    ) -> List[Union[types.TextContent, types.ImageContent, types.EmbeddedResource]]:
        update_dag_run_state = UpdateDagRunState(state=state)
        response = dag_run_api.update_dag_run_state(
            dag_id=dag_id,
            dag_run_id=dag_run_id,
            update_dag_run_state=update_dag_run_state,
        )
        return [types.TextContent(type="text", text=str(response.to_dict()))]
  • The registration function that includes the 'update_dag_run_state' tool in the list of tools to be registered with MCP.
    def get_all_functions() -> list[tuple[Callable, str, str, bool]]:
        """Return list of (function, name, description, is_read_only) tuples for registration."""
        return [
            (post_dag_run, "post_dag_run", "Trigger a DAG by ID", False),
            (get_dag_runs, "get_dag_runs", "Get DAG runs by ID", True),
            (get_dag_runs_batch, "get_dag_runs_batch", "List DAG runs (batch)", True),
            (get_dag_run, "get_dag_run", "Get a DAG run by DAG ID and DAG run ID", True),
            (update_dag_run_state, "update_dag_run_state", "Update a DAG run state by DAG ID and DAG run ID", False),
            (delete_dag_run, "delete_dag_run", "Delete a DAG run by DAG ID and DAG run ID", False),
            (clear_dag_run, "clear_dag_run", "Clear a DAG run", False),
            (set_dag_run_note, "set_dag_run_note", "Update the DagRun note", False),
            (get_upstream_dataset_events, "get_upstream_dataset_events", "Get dataset events for a DAG run", True),
        ]
  • Import of the UpdateDagRunState schema/model used for structuring the input parameters in the handler.
    from airflow_client.client.model.update_dag_run_state import UpdateDagRunState
  • Initialization of the DAGRunApi client instance used by the handler.
    dag_run_api = DAGRunApi(api_client)
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Update' implying mutation, but doesn't disclose behavioral traits like required permissions, whether the operation is reversible, what happens to dependent tasks, or if it triggers downstream effects. For a mutation tool with zero annotation coverage, this is a significant gap.

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?

Single sentence, front-loaded with the core action, zero waste. It efficiently conveys the essential purpose without unnecessary words.

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?

Given complexity (mutation tool with 3 parameters), no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It lacks details on behavior, parameter meanings, return values, and usage context, making it inadequate for safe and effective tool invocation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It mentions 'DAG ID and DAG run ID' but doesn't explain the 'state' parameter (e.g., valid values like 'success', 'failed', or 'running', or that null might reset to default). With 3 parameters and no schema descriptions, the description adds minimal value beyond naming two of them.

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 action ('Update') and target resource ('DAG run state'), specifying it requires DAG ID and DAG run ID. It distinguishes from siblings like 'set_task_instances_state' by focusing on DAG runs rather than tasks, but doesn't explicitly contrast with 'clear_dag_run' or 'delete_dag_run'.

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?

No guidance on when to use this tool versus alternatives like 'clear_dag_run', 'delete_dag_run', or 'set_task_instances_state'. It doesn't mention prerequisites (e.g., DAG must exist) or typical scenarios (e.g., manual state changes for workflow management).

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/nikhil-ganage/mcp-server-airflow-token'

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