Skip to main content
Glama

Linkup batch tasks (create)

linkup-tasks-create

Create up to 100 asynchronous Linkup search, fetch, research, or extract tasks in one batch for bulk or long-running work; optionally validate and estimate cost without submitting.

Instructions

Create a batch of asynchronous tasks (POST /v1/tasks). Each task is billed exactly like the direct call: search 0.005 to 0.055, fetch 0.001 to 0.011, research 0.25 to 2.50 (100 research tasks at the default depth L cost 150 USD), extract variable (2 to 10 typical). There is no batch discount; Tasks is for bulk, long-running or mixed work, not for single calls.

Returns the task envelopes (id, type, status pending, input, output null). Then poll with linkup-tasks-list (bulk, every 5 s for research, 1 to 2 s for search and fetch) or linkup-tasks-get (one task). A failing task does not fail the batch and is not billed. The organisation has a concurrency quota (see quota in linkup-tasks-list); above it the API answers 429. Results are kept for a bounded period: store them when they complete.

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": {
      "tasks": "<tasks>"
    },
    "name": "linkup-tasks-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
tasksYes1 to 100 items, each {"type": "search" | "fetch" | "research" | "extract", "input": {...}} where input has exactly the fields of the matching endpoint (camelCase: q, depth, outputType, url, renderJs, mode, reasoningDepth, includeDomains, fromDate ...). Types can be mixed. Tasks run in parallel; submit dependent work (fetch after search) as a second batch.
dry_runNotrue: validate and return the cost estimate without submitting anything.

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 a non-read-only, open-world, non-idempotent, non-destructive write, and the description adds substantial non-schema behavior: exact per-type pricing, no batch discount, partial-failure semantics (a failing task does not fail the batch and is not billed), a concurrency quota with 429 responses, and bounded result retention. Minor gap: it doesn't say how to detect quota size beyond pointing at linkup-tasks-list's quota field, or what happens when a batch is partially rejected.

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 action and endpoint, then pricing, then return shape and polling path — a sensible order. The dense cost enumeration (0.005 to 0.055, 0.001 to 0.011, 0.25 to 2.50) is useful but the most verbose block; everything else earns its place.

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?

For a mutation tool with no output schema, the description covers what comes back (task envelopes with id, type, pending status, input, output null), how to observe completion, failure billing behavior, quota limits, and result retention. Nothing essential to correct invocation is missing.

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 100% and both parameters are already richly documented in the schema, including the 1-100 item shape and type-specific input fields. The description supplements this with meaning the schema can't convey — default-depth research cost math and the parallel-execution/ordering constraint that dependent work must be a second batch.

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 plus the underlying endpoint ("Create a batch of asynchronous tasks (POST /v1/tasks)"), and explicitly scopes it against single calls: "Tasks is for bulk, long-running or mixed work, not for single calls." An agent can distinguish this from linkup-search/linkup-research/linkup-fetch without opening any schema.

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?

Gives explicit when-to-use (bulk, long-running, mixed work) and when-not (single calls), and routes follow-up work to concrete alternatives: linkup-tasks-list for bulk polling at named intervals, linkup-tasks-get for one task. It also tells the agent to submit dependent work as a second batch rather than chaining within one batch.

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