Skip to main content
Glama

Linkup rewind search (beta)

linkup-rewind-search
Read-only

Search the web as it existed at the end of a specific UTC day, returning results with content, URLs, and revision validity dates.

Instructions

Search the web as it was at the end of a given UTC day (POST /v1/rewind/search). CLOSED BETA: 403 unless enabled for the organisation. Returns results with content, name, url, validFrom and validTo (the first day the revision was no longer visible, null if current).

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": {
      "query": "<query>",
      "as_of": "<as_of>"
    },
    "name": "linkup-rewind-search"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofYesUTC day to search as of, YYYY-MM-DD.
queryYes
max_charsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, open-world, non-idempotent), and the description adds genuinely new behavioral facts: an access gate that yields 403, and the exact result shape including the subtle meaning of validTo (first day the revision was no longer visible, null if current). It stops short of stating result counts, pagination, or rate limits, which keeps it at 4 rather than 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Three tight sentences, front-loaded with what the tool does, followed by the access constraint and the return shape. No filler and nothing repeated from the annotations or schema.

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

Completeness3/5

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

Explaining the return fields is the right move given there is no output schema, and the beta gating is a valuable addition. But for a 3-parameter tool the description leaves two parameters (query, max_chars) with no semantic coverage anywhere, which is a real completeness gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%: as_of is documented, but query and max_chars are not described in the schema and get no mention in the description at all. The description adds only a mild gloss on as_of ("end of a given UTC day"), leaving max_chars semantics such as truncation behavior entirely unexplained.

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?

The description gives a specific verb and resource ("Search the web as it was at the end of a given UTC day") plus the concrete endpoint POST /v1/rewind/search. The temporal-scope qualifier is what distinguishes it from a plain web search sibling like linkup-search, so an agent can route without opening another schema.

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 historical-search framing implies when this tool applies, and the CLOSED BETA note usefully warns that calls fail with 403 unless enabled for the organisation. However, it never explicitly says to prefer linkup-search for current results or linkup-rewind-fetch for retrieving a known historical document, so the choice between siblings is left to inference.

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