Skip to main content
Glama

Linkup rewind fetch (beta)

linkup-rewind-fetch
Read-only

Retrieve a webpage as it appeared at the end of a specified UTC day by supplying the exact stored URL and YYYY-MM-DD date.

Instructions

Return a page as it was at the end of a given UTC day (POST /v1/rewind/fetch). CLOSED BETA: 403 unless enabled; 404 when no revision is visible that day; 422 when the day is not available.

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

Input Schema

NameRequiredDescriptionDefault
urlYesExact stored URL, no normalisation is applied.
as_ofYesUTC day, YYYY-MM-DD.
max_charsNo

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 readOnlyHint=true, openWorldHint=true, destructiveHint=false and idempotentHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: CLOSED BETA gating with 403 unless enabled, 404 when no revision is visible, and 422 when the day is not available. It does not explain why the call is non-idempotent (snapshot/content drift) or what auth the beta requires.

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?

Two tightly packed sentences with zero waste: purpose and endpoint first, then the beta gate and HTTP status semantics. Every clause carries information an agent needs before calling.

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?

With no output schema, the description should say what the returned 'page' looks like (format, whether content is truncated by max_chars, how revisions surface), and it does not. Error and beta semantics are well covered, but return-shape and the unexplained max_chars parameter leave a real gap for a fetch tool.

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 67%, with url and as_of already fully documented in the schema; only max_chars lacks a description. The description adds a small amount of meaning by pinning as_of to an end-of-day snapshot boundary, but says nothing about max_chars truncation behavior or URL normalization beyond what the schema states.

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?

The description gives a specific verb and resource ('Return a page as it was at the end of a given UTC day') plus the underlying endpoint, which makes the historical-snapshot nature explicit versus a live fetch. It never names a sibling such as linkup-fetch, so the differentiation is inferred from the 'as it was' phrasing rather than stated.

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?

Usage is only implied: the agent must infer that this is the tool for retrieving a past state of a known URL rather than searching history (linkup-rewind-search exists as a sibling but is not mentioned). No explicit when-not or alternative-selection guidance is given, though the 403/404/422 failure modes indirectly tell the agent when the call will not succeed.

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