Skip to main content
Glama
nikhil-ganage

MCP Server Airflow Token

delete_dataset_queued_events

Remove queued Dataset events from Apache Airflow to manage event backlog and optimize workflow performance.

Instructions

Delete queued Dataset events for a Dataset

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uriYes
beforeNo

Implementation Reference

  • The main handler function that implements the tool logic. It calls the Airflow DatasetApi to delete queued events for a given dataset URI, optionally before a certain timestamp.
    async def delete_dataset_queued_events(
        uri: str,
        before: Optional[str] = None,
    ) -> List[Union[types.TextContent, types.ImageContent, types.EmbeddedResource]]:
        kwargs: Dict[str, Any] = {}
        if before is not None:
            kwargs["before"] = before
    
        response = dataset_api.delete_dataset_queued_events(uri=uri, **kwargs)
        return [types.TextContent(type="text", text=str(response.to_dict()))]
  • Registration of the tool in the get_all_functions() list, which is used to register MCP tools.
        delete_dataset_queued_events,
        "delete_dataset_queued_events",
        "Delete queued Dataset events for a Dataset",
        False,
    ),
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 this is a deletion operation, implying it's destructive, but doesn't disclose critical behavioral traits: whether deletion is permanent or reversible, what permissions are required, if there are rate limits, or what happens to associated data. For a destructive 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?

The description is a single, efficient sentence with zero wasted words. It's appropriately sized for a simple tool and front-loads the core action and target.

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?

For a destructive deletion tool with 2 parameters, 0% schema coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain what 'queued events' are, the deletion's impact, parameter meanings, or expected outcomes. The context demands more comprehensive guidance.

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 schema provides no parameter documentation. The description mentions 'for a Dataset' which hints at the 'uri' parameter's purpose, but doesn't explain what 'uri' represents or the optional 'before' parameter's role. With 2 parameters completely undocumented, the description adds minimal semantic value.

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 ('Delete') and target resource ('queued Dataset events for a Dataset'), making the purpose understandable. However, it doesn't distinguish this tool from its sibling 'delete_dag_dataset_queued_event' or 'delete_dag_dataset_queued_events', which appear to perform similar operations on different resources.

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 is provided on when to use this tool versus alternatives. With multiple deletion tools in the sibling list (e.g., delete_dag_dataset_queued_event, delete_dag_dataset_queued_events), the description offers no context about differences in scope, prerequisites, or appropriate use cases.

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