Skip to main content
Glama

Linkup extract rows (download)

linkup-extract-download
Read-onlyIdempotent

Download the NDJSON result of a completed extract task and return its rows as JSON, with options to cap returned rows and JSON size. Use it to retrieve extracted data after a task finishes.

Instructions

Download the NDJSON result of a completed extract task and return its rows as JSON. Free (the download link in the task output is a plain file URL, valid 24 hours).

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-extract-download"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCompleted extract task id.
max_rowsNoMaximum rows to return.
max_charsNoCap on the returned JSON size.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the safety profile is covered. The description adds behavior the annotations cannot: the underlying artifact is NDJSON, returned rows are re-serialized as JSON, the operation is free, and the source file URL expires after 24 hours. That expiry note is the kind of time-sensitive detail an agent could not infer.

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 short sentences: the action first, then the cost and expiry caveat in parentheses. Nothing is redundant and the key behavior is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With three well-documented params and no output schema, the description should say something about the shape of the returned JSON and what happens when max_rows or max_chars is hit — silent truncation versus an explicit signal matters a lot for a row-extraction tool. It says 'rows as JSON' but not whether there is an envelope, truncation flag, or continuation mechanism. Adequate to invoke, incomplete for interpreting results.

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% — id, max_rows, and max_chars each carry their own titles, bounds, and defaults. The description adds no meaning beyond that, not even a note on how max_chars interacts with max_rows. Baseline 3 is appropriate when the schema does the work.

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 states a specific verb and resource: download the NDJSON result of a completed extract task and return its rows as JSON. That distinguishes it from a task-metadata getter like linkup-get-extract by implication, and the source/target format detail is concrete. It stops short of naming a sibling to route against, so it is clear but not fully differentiated.

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?

The phrase 'completed extract task' implies the precondition that the task must already be finished, which is genuine usage context. However, it never says what to do if the task isn't complete (e.g., use the get/status sibling first) or when to prefer this over reading the task output directly, leaving the routing implicit.

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