Skip to main content
Glama

Linkup tasks (list)

linkup-tasks-list
Read-onlyIdempotent

List and filter an organization's tasks by type or status with pagination, previews, and quota metadata. Use this bulk poll instead of many individual task lookups.

Instructions

List the organisation's tasks of all types (GET /v1/tasks). Free. Returns data (task envelopes with an output_preview, or full outputs with include_output), metadata (page, pageSize, total, totalPages) and quota (inFlight: tasks pending or processing now; limit: maximum concurrent tasks allowed). Prefer this bulk poll over many linkup-tasks-get calls; the poll cap is 1 request per second.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
typeNoFilter by task type(s).
statusNoFilter by status(es).
sort_byNo
max_charsNoCap on the returned JSON size.
page_sizeNo1 to 100.
include_outputNotrue: include each task's full output (large). Default: a short output_preview per task; read one task with linkup-tasks-get.
sort_directionNoAPI default asc; desc for newest first.desc

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/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 real value beyond them: cost ('Free'), the throughput constraint (1 request/second), and the exact response envelope (data, metadata with page/pageSize/total/totalPages, quota with inFlight and limit semantics). It stops short of describing pagination behavior when totalPages is exceeded, so not 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.

Conciseness4/5

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

Front-loaded with the verb, scope and endpoint, then cost, then return shape, then the alternative — a sensible priority order. The quota parenthetical is informative but dense, and 'Free.' as a standalone fragment is slightly clipped, keeping it just below top marks.

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

Completeness5/5

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

Eight optional parameters and no output schema, yet the description pre-empts the biggest unknowns by spelling out the response structure (data/metadata/quota) and the include_output size implication. Quota semantics (inFlight vs limit) are explained, which is exactly the context an agent needs when polling.

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 75%, so the baseline is 3; the description earns above that by explaining the key include_output tradeoff ('task envelopes with an output_preview, or full outputs with include_output') and by surfacing page/pageSize/total from the metadata. The type, status, sort_by and sort_direction filters are left entirely to the schema, which caps it at 4.

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 ('List the organisation's tasks of all types') plus the underlying endpoint GET /v1/tasks, and the scope ('all types') is immediately clear. An agent can distinguish it from linkup-tasks-get, which the description names as the single-task alternative.

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

Usage Guidelines5/5

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

Explicitly instructs 'Prefer this bulk poll over many linkup-tasks-get calls', naming the alternative and the condition that selects this tool. It also discloses the poll cap of 1 request per second, which shapes how an agent should schedule calls rather than fan out individual gets.

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