mcp-archive

list_snapshots

List Wayback Machine snapshots for a given URL, with optional date range filtering.

Instructions

List Wayback snapshots for a URL, optionally filtered by date range.

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": "list_snapshots"
  }
}

Input Schema

Name	Required	Description
`url`	Yes
`from`	No	ISO date (YYYY-MM-DD)
`to`	No	ISO date (YYYY-MM-DD)
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 14, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description carries full burden but fails to disclose behavioral traits such as pagination, rate limits, or whether it returns metadata only. It merely states the basic function.

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?

Single sentence, 10 words, no redundancy. Front-loaded with key action and resource. Highly concise.

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

Completeness2/5

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

Given four parameters, required url, no output schema, and multiple sibling tools, the description lacks completeness. It does not explain return format, pagination (implied by limit), or differentiation from get_archived and search_archive_items.

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 description coverage is 50% (from and to have descriptions). The description adds 'optionally filtered by date range' but does not clarify url or limit beyond schema. Baseline 3 is appropriate as description adds minimal extra value.

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 Wayback snapshots for a URL, with optional date range filtering. It uses specific verbs and resource, and distinguishes from siblings like compare_snapshots or fetch_archived_text.

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 snapshots with filters but does not provide explicit guidance on when to use this tool versus alternatives like search_archive_items. No exclusions or when-not-to-use advice.

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

Deploy Server