Skip to main content
Glama

Linkup extract task (get)

linkup-get-extract
Read-onlyIdempotent

Retrieves the status and results of a single extraction task by ID, returning credit usage, row count, and a 24-hour NDJSON download link when complete.

Instructions

Read one extract task (GET /v1/extract/{id}). Free. When completed, output holds creditsUsed, rowsReturned and resultUrl (an NDJSON download link valid for 24 hours); the rows are not in the response.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "linkup-get-extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: the call is free (cost implication), the completed response contains creditsUsed, rowsReturned and resultUrl, that link expires in 24 hours, and crucially that the rows themselves are NOT in the response. It stops short of describing pending/failed states or error behavior, keeping it from a 5.

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?

Two sentences, front-loaded with the action and endpoint, then cost, then the output contract. The parenthetical about the 24-hour NDJSON link and the closing warning that rows are absent each earn their place by preventing a common mistake.

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?

With no output schema, the description does the important work of naming the return fields and explaining the download indirection. The remaining gap is lifecycle behavior: what the response looks like while the task is still running or has failed, and how to actually fetch the rows once resultUrl is obtained.

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

Parameters4/5

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

Schema coverage is 0% and the only field is bare "Id" with minLength 1, so the description carries the burden. It does so partially by tying id to the extract task identifier via the /v1/extract/{id} path, which tells the agent this is a task id and not a generic identifier. It could still be more explicit that this is the id returned by the extract creation call.

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 pairs a specific verb and resource ("Read one extract task") with the concrete endpoint GET /v1/extract/{id}. The word "one" plus the endpoint path distinguishes it from the list variant, and the mention of resultUrl signals the separate download step, so an agent can place it in the workflow without opening siblings.

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?

"When completed" implies this is a polling/status-check tool for an already-created extract task, which is useful implicit guidance. However, it never states what to do while the task is pending, whether to poll or use a wait tool, or when to prefer linkup-list-extract or linkup-extract-download instead.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.