Skip to main content
Glama

Linkup extract tasks (list)

linkup-list-extract
Read-onlyIdempotent

List extraction tasks with pagination and sorting to track Linkup extract job status and history.

Instructions

List extract tasks (GET /v1/extract). Free. Closed beta.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
sort_byNo
page_sizeNo
sort_directionNodesc

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 openWorld, so safety is covered; the description adds cost ('Free') and an availability constraint ('Closed beta') that annotations cannot express. It does not describe pagination behavior or what a task record contains, but the annotation bar is already met.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short fragments with zero filler, and the operation is front-loaded before the endpoint, cost and availability notes. It is terse to the point of omitting useful detail, but nothing present is wasted.

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 no output schema, the description is not obliged to describe return values, and annotations cover the safety profile. However, for a paginated list tool with four undocumented parameters, an agent gets no sense of result volume, ordering default behavior, or beta-related failure modes.

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?

All four parameters (page, page_size, sort_by, sort_direction) have 0% schema description coverage, and the description says nothing about paging or sorting semantics. The schema's titles, defaults and min/max are partly self-explanatory, but the description does not compensate for the documented coverage gap.

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?

States a specific verb+resource ('List extract tasks') and even names the underlying endpoint (GET /v1/extract), which lets an agent distinguish it from single-item siblings like linkup-get-extract. It stops short of explicitly naming an alternative for the 'list my tasks vs. list research' case.

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?

'Free' and 'Closed beta' communicate cost and availability, which implicitly tells an agent when this call is cheap and when it may fail. There is no explicit when-to-use vs. when-to-use-another-tool guidance, and no note on how this differs from linkup-tasks-list or linkup-list-research.

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