Skip to main content
Glama

lookup_snapshots

Query the Wayback Machine for snapshots of a URL, with options to filter by date range, HTTP status code, and collapse duplicates based on timestamp or digest.

Instructions

Return CDX snapshots for a URL, with optional date range and status-code filter.

The Wayback Machine often crawls the same URL many times per day; raw CDX results would return one row per crawl. collapse is a server-side de-duplication: adjacent rows that share the same value in the chosen field get folded into a single representative row.

By default we collapse on the first 8 digits of the timestamp ("timestamp:8"), which is the YYYYMMDD prefix — i.e. one row per day. This is almost always what you want for "show me snapshots of this URL"; otherwise the default limit of 50 gets eaten by 50 captures from a single hour and you see nothing about the URL's history.

Override collapse when you need different granularity:

  • "digest" — collapse on content hash, so you only see captures where the page actually changed

  • "timestamp:10" — one row per hour (first 10 digits of timestamp)

  • "" (empty string) — disable collapsing entirely; return every capture

  • any other CDX collapse spec is passed through verbatim

latest=True uses CDX's fastLatest path to return the N most recent captures cheaply (much faster than a full scan over the index). Cannot be combined with from_date/to_date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
from_dateNo
to_dateNo
status_codeNo
limitNo
collapseNo
latestNo
Behavior4/5

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

Without annotations, the description discloses default collapse behavior, limit consumption, and the constraint that latest cannot combine with date range, offering good behavioral insight.

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?

The description is front-loaded with the main purpose and structured with clear sections, though slightly lengthy; each sentence is informative.

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?

Given no output schema or annotations, the description covers main purpose, key behaviors, and important parameters, though it lacks output format or error handling details.

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?

The description adds significant value for collapse and latest parameters with detailed examples, but covers other parameters only in passing, partially compensating for 0% schema description coverage.

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 clearly states the tool returns CDX snapshots for a URL with optional date range and status-code filters, differentiating it from sibling tools like get_snapshot_content.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use different collapse options and the latest parameter, providing context for choosing among them, but does not explicitly compare to sibling tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lakshyamehta03/wayback-machine-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server