Skip to main content
Glama
Sign In

Wayback

by io.github.pipeworx-io
OverviewDiscussionsAdmin

List Snapshots

list_snapshots
Read-onlyIdempotent

List the captured snapshots of a URL in the Internet Archive Wayback Machine over time, using the CDX index. Each entry includes the capture timestamp, the original URL, HTTP status code, MIME type, content digest and a direct Wayback snapshot URL. Optionally restrict to a date range with from/to (YYYYMMDD).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "https://example.com"
    },
    "name": "list_snapshots"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOptional end of date range as YYYYMMDD.
urlYesThe page URL to list archived snapshots for, e.g. "example.com".
fromNoOptional start of date range as YYYYMMDD.
limitNoMaximum number of snapshots to return (default 50, max 1000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "url": "https://example.com"
+  },
+  {
+    "from": "20190101",
+    "limit": 100,
+    "to": "20210101",
+    "url": "https://example.com/page"
+  }
+]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, establishing safe behavior. The description adds value by detailing the output fields and date format constraints, beyond what annotations provide. No contradictions.

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?

The description is two sentences, front-loaded with the core action. Every sentence provides essential information without redundancy.

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?

For a simple listing tool, the description covers the purpose, output structure, optional date range, and constraints. No output schema exists, so the description appropriately describes return fields. Annotations cover safety and idempotency.

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 100%, so baseline is 3. The description reinforces the meaning of from/to as date range parameters with YYYYMMDD format, but this is already clear from the schema. No additional semantic depth beyond the schema.

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 lists snapshots of a URL from the Internet Archive Wayback Machine, specifying key fields (timestamp, URL, status, MIME, digest, Wayback URL) and the use of the CDX index. This distinguishes it from siblings like get_snapshot (single snapshot) and get_capture_count (count only).

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 for listing multiple snapshots with optional date range restriction, but does not explicitly state when to use this tool versus alternatives (e.g., get_snapshot for a single capture). No exclusions or when-not-to-use guidance are provided.

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

All Wayback toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources