Skip to main content
Glama

Linkup task (get)

linkup-tasks-get
Read-onlyIdempotent

Retrieve a single Linkup task by ID to check its status and inspect the output, including result URLs for extract tasks.

Instructions

Read one task of any type (GET /v1/tasks/{id}). Free. status: pending, processing, completed, failed. output has the same shape as the matching synchronous endpoint; for extract tasks it holds resultUrl (download with linkup-extract-download).

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-tasks-get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTask id (search, fetch, research or extract task).
max_charsNoCap on the returned JSON size.

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 cover read-only, idempotent, non-destructive and open-world. The description adds genuinely new facts: the call is free (no credit cost), the full status lifecycle values (pending/processing/completed/failed), and that output mirrors the matching synchronous endpoint, with extract tasks carrying resultUrl. It omits anything about rate limits or whether output can be truncated.

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?

Three short sentences, front-loaded with the verb, resource and endpoint, then cost, then status/output semantics. The fragment 'Free.' is terse but earns its place by answering a real cost question.

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 carries the burden of describing return values and does so by reference to the matching synchronous endpoint, plus the extract-specific resultUrl note. That reference is slightly indirect, but an agent has enough to call the tool and interpret the response.

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% and both parameters are documented there, so the baseline is 3. The description adds no further detail about the id format or what max_chars truncation does to the returned JSON.

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?

States a specific verb and resource ('Read one task of any type') plus the underlying endpoint GET /v1/tasks/{id}, which unambiguously separates it from linkup-tasks-list and the create tool. The scope 'of any type' plus the enumerated task types makes the breadth of the tool explicit.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context for use: single-task retrieval by id, and explicitly routes extract-task results to linkup-extract-download for downloading resultUrl. It does not state when not to use it (e.g., listing or waiting on tasks), but the 'one task' framing makes that boundary reasonably clear.

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