Skip to main content
Glama

get_task_instance_extra_links

Retrieve additional links for Airflow task instances to access logs, documentation, or external resources associated with specific DAG runs and tasks.

Instructions

[Tool Role]: Gets extra links for a task instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dag_idYes
dag_run_idYes
task_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function decorated with @mcp.tool() that implements the tool logic by querying the Airflow API for extra links of a specific task instance.
    async def get_task_instance_extra_links(dag_id: str, dag_run_id: str, task_id: str) -> Dict[str, Any]:
        """[Tool Role]: Gets extra links for a task instance."""
        resp = await airflow_request("GET", f"/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances/{task_id}/links")
        resp.raise_for_status()
        return resp.json()
Behavior1/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the action 'gets' without detailing permissions, rate limits, response format, or side effects. This leaves the agent unaware of critical operational aspects, such as whether this is a read-only operation or if it requires specific authentication.

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 extremely concise with a single sentence, front-loaded and free of unnecessary words. However, this brevity comes at the cost of under-specification, but as per scoring rules, it earns a high score for efficiency in structure.

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 the complexity of a 3-parameter tool with no annotations and 0% schema coverage, the description is incomplete. While an output schema exists (which mitigates the need to explain return values), the lack of parameter semantics, usage guidelines, and behavioral transparency makes it inadequate for effective tool invocation.

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

Parameters1/5

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

Schema description coverage is 0%, and the description provides no information about the parameters (dag_id, dag_run_id, task_id). It does not explain what these IDs represent, their format, or how they relate to 'extra links', failing to compensate for the lack of schema documentation.

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

Purpose2/5

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

The description 'Gets extra links for a task instance' restates the tool name with minimal elaboration, making it tautological. It specifies the verb 'gets' and resource 'extra links for a task instance', but lacks detail on what 'extra links' are or how this differs from sibling tools like get_task_instance_details or get_task_instance_logs, leaving the purpose vague.

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

Usage Guidelines1/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. The description does not mention prerequisites, context, or exclusions, and with many sibling tools (e.g., get_task_instance_details, get_task_instance_logs), there is no indication of how this tool fits into the workflow, leading to potential misuse.

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