Skip to main content
Glama

Find Wayback Machine snapshots of a URL

web_archive
Read-only

Wayback Machine snapshots of a public URL: the capture closest to a date, the list of captures in a date range (one per day, max 500), first and last capture, and mode=diff, which compares the latest snapshot's text with the live page (added and removed lines, max 200 each). Diff is line-based and does not parse JavaScript-rendered pages. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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>"
    },
    "name": "web_archive"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoCaptures up to this date, YYYY-MM-DD (optional)
urlYesPublic http(s) URL to look up
dateNoClosest snapshot to this date, YYYY-MM-DD (optional)
fromNoCaptures from this date, YYYY-MM-DD (optional)
modeNocaptures (default) or diff

Output Schema

NameRequiredDescriptionDefault
urlNo
lastNo
firstNo
sourceNo
closestNo
capturesNo
checkedAtNo
captureCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing the cost model ($0.002 per successful call, x402 with USDC on Base, Solana and 10+ networks), that failed calls are not charged, result caps (500 captures, 200 added/removed lines), and the JS-rendering limitation of diff. These are exactly the operational facts an agent needs before spending money on a call.

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-loads the resource and mode inventory, then closes with cost and limitations; every clause carries information. It is a single very dense sentence with stacked parentheticals, which costs a little readability but wastes no words.

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?

With an output schema present, the description need not describe return shapes, and it still covers caps, diff semantics, rendering caveats, and payment terms. Nothing material for correct invocation of this 5-parameter, open-world, paid tool 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%, so the baseline is 3, but the description adds real meaning: it explains that from/to yield one capture per day capped at 500, that date selects the closest snapshot, and that mode=diff compares the latest snapshot text against the live page. Only the exact interaction between date and from/to is left implicit.

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?

Opens with a specific resource and scope ("Wayback Machine snapshots of a public URL") and then enumerates the four query shapes the tool supports: closest-to-date capture, range list, first/last capture, and diff. An agent can immediately tell this is a historical-archive lookup, distinct from siblings like certs or ai_crawlers.

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 description implies usage through the mode enumeration and gives one explicit when-not (diff is line-based and does not parse JavaScript-rendered pages). However, it never names or points to an alternative tool, nor states when to prefer a live fetch or a different sibling over an archive lookup, so routing guidance is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources