Skip to main content
Glama

Linkup responses (OpenAI-style)

linkup-responses
Read-only

Generate web-grounded answers in OpenAI Responses format with URL citations, so clients can use Linkup as an OpenAI-compatible base URL for chat workflows.

Instructions

Generate a web-grounded answer in the OpenAI Responses format (POST /v1/responses). This is the endpoint behind using Linkup as an OpenAI-compatible base URL. Returns output_text and output messages with url_citation annotations. Its price is not published on the pricing page (read 2026-11-13); check linkup-credits-balance before and after if it matters. For most uses linkup-search with sourcedAnswer is the simpler call.

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": {
      "input": "<input>"
    },
    "name": "linkup-responses"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesA question string, or a list of messages [{"role": "user" | "assistant" | "developer", "content": "..."}].
modelNolinkup-standard answers faster; linkup-deep takes longer and is more comprehensive.linkup-standard
max_charsNo
text_formatNoOptional JSON Schema (root type object) for structured text output; omit for plain text.
instructionsNoSystem-message-like guidance for the answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover safety (readOnly, non-destructive, openWorld) and non-idempotency; the description adds value on top by disclosing the return shape (output_text plus output messages with url_citation annotations) and an unpublished price point. The main residual gap is that latency/rate-limit behavior is only hinted at indirectly via the schema's model description, so it falls just short of 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 core purpose, then cost caveat, then the alternative recommendation — a sensible priority order. It is slightly dense at five sentences with a dated parenthetical, but each sentence carries distinct 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 does the necessary work of describing the response shape (output_text, output messages, url_citation annotations) and the cost-verification workflow. Given 5 parameters at 80% schema coverage and existing annotations, nothing essential for a correct call is missing.

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 description coverage is 80%, so the schema already explains input, model, text_format, and instructions. The description adds no parameter-level detail of its own beyond implying that text_format controls the plain-text-vs-structured output, so the baseline 3 is appropriate.

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?

Names a specific verb and resource ('Generate a web-grounded answer') and pins it to a concrete protocol surface ('OpenAI Responses format, POST /v1/responses'), plus the OpenAI-compatible-base-URL framing. This clearly separates it from the plain search siblings, so an agent can route without opening the 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?

Explicitly routes the agent away for the common case: 'For most uses linkup-search with sourcedAnswer is the simpler call,' naming both the alternative and the condition. It also gives a concrete operational rule — check linkup-credits-balance before and after when cost matters — which is real when-to-use guidance, not boilerplate.

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