Skip to main content
Glama

Linkup API guide

linkup-guide
Read-onlyIdempotent

Explains Linkup API endpoints, parameters, pricing, latencies, limits, and polling rules, plus best practices for search, fetch, research, and batch tasks.

Instructions

Explain the Linkup API: endpoints, parameters, prices, latencies, limits, polling rules and best practices, condensed from Linkup's documentation (read 2026-11-13). Free, no network.

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

Input Schema

NameRequiredDescriptionDefault
topicNoWhich part of the guide to return.overview

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 cover the safety profile (read-only, closed-world, idempotent, non-destructive), so the bar is lower; the description adds real value beyond them by disclosing that the content is a static condensation of Linkup's documentation read on 2026-11-13, which tells the agent the guide may be stale, and that the call costs nothing and touches no network.

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?

One dense sentence plus a short clause; the cost/offline caveat is front-loaded at the end of the sentence rather than buried. The content list is long but each item is substantive rather than filler.

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 one optional enum parameter and no output schema, the description correctly carries the burden of saying what comes back, and it does so by enumerating the covered subjects and naming the source and read date. Only the absence of explicit sibling routing keeps it from being complete.

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% and the single optional `topic` parameter carries a full enum with default and per-value description, so the schema does the heavy lifting. The description's enumeration of guide contents (prices, latencies, limits, polling rules) loosely maps onto the topic values but adds no selector guidance or mapping.

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 ("Explain the Linkup API") and enumerates the content returned: endpoints, parameters, prices, latencies, limits, polling rules, best practices. This makes it clearly distinct from the action-performing siblings (linkup-search, linkup-fetch, linkup-research), though it never names a sibling explicitly.

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, no network" implies this is a zero-cost orientation/help call and hints at when to prefer it over a real API call, but there is no explicit when-to-use or when-not statement and no routing to siblings such as linkup-search when the agent actually wants data.

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