Skip to main content
Glama

Linkup research tasks (list)

linkup-list-research
Read-onlyIdempotent

List and page through your organisation’s research tasks, with status, errors, timestamps, and output previews or full outputs, so you can track runs and choose tasks to inspect.

Instructions

List the organisation's research tasks (GET /v1/research). Free.

Returns data (tasks, each with id, status, input, error, createdAt, updatedAt and an output_preview, or the full output with include_output) and metadata (page, pageSize, total, totalPages). Results are kept for a bounded period; store what you need.

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-research"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, from 1.
sort_byNoSort field.
max_charsNoCap on the returned JSON size.
page_sizeNoTasks per page, 1 to 100.
include_outputNotrue: include each task's full output (large). Default: a short output_preview per task; read one task with linkup-get-research.
sort_directionNoAPI default asc; use desc for newest first.desc

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 and non-destructive, so safety is covered. The description adds genuinely new behavior: the call is free, and results are retained only for a bounded period so the caller should persist them — a real operational caveat. Pagination metadata and the preview-vs-full-output tradeoff are also disclosed.

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 and resource, then the return shape, then the retention caveat — a sensible order with little waste. The standalone 'Free.' sentence is terse but does convey cost information.

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 returns and does so well: enumerated task fields, output_preview versus full output, and page/pageSize/total/totalPages metadata. Only minor gaps remain, such as filtering or error behavior on empty result sets.

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 coverage is 100%, so every parameter is already documented, including include_output, page_size and max_chars. The description reinforces include_output (full output vs output_preview) and the paging metadata but adds no syntax or format detail beyond the schema; baseline 3 applies.

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 and resource ('List the organisation's research tasks') and even names the underlying endpoint (GET /v1/research), so the agent knows exactly what it retrieves. It does not explicitly differentiate itself from near-name siblings like linkup-tasks-list or linkup-list-extract, which keeps it from a 5.

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 description implies usage (browse/list tasks, store results because of bounded retention) and flags that the call is free, but it never says when to choose this over linkup-get-research or linkup-tasks-list. The guidance about reading one task with linkup-get-research lives in the schema, not the description.

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