Skip to main content
Glama
smeet666

mcp-archiveorg

List captures of a page

list_snapshots
Read-onlyIdempotent

List a web page's Wayback Machine captures from oldest to newest, showing capture dates to reveal how long and how often it has been archived. Page through older captures with a cursor.

Instructions

List Wayback Machine captures of a web page, oldest first, with the dates they were taken. Answers how long a page has been archived and how often, which get_snapshot cannot. Identical consecutive captures are collapsed, so a date marks a visit on which the page was seen to differ from the previous one. A capture records when the crawler came, not when the page changed: the change happened somewhere between two dates. This route is slow, tens of seconds on a heavily archived address, and it is paged for that reason. To walk further back, pass the 'next_cursor' from the previous answer as 'cursor'. The index counts rows rather than positions, so there is no page number and no arithmetic to do: a null 'next_cursor' means the end of what it holds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesAddress to look up.
limitNoCaptures to return.
cursorNoThe 'next_cursor' from a previous answer. Omit to start at the oldest capture.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
lastYesLatest capture in this answer, not in the whole history.
firstYesEarliest capture in this answer, not in the whole history.
notesYes
returnedYesCaptures in this answer.
snapshotsYes
next_cursorYesPass back as 'cursor' to read the window after this one. Null at the end of the history.
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description explains important behavioral quirks: identical consecutive captures are collapsed, capture dates indicate when the crawler visited rather than when the page changed, and the route is slow and paged. This adds significant context beyond annotations.

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 relatively long but every sentence adds value, from purpose to behavioral details to pagination mechanics. It is well-structured, front-loaded with the main purpose, and avoids irrelevant filler.

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?

Given the tool's complexity (pagination, special semantics, performance caveats), the description covers all essential aspects: what it returns, how to interpret results, how to paginate, and how to detect the end. It even introduces the sibling for comparison. The output schema exists, so return fields need not be repeated.

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 baseline is 3. The description adds extra conceptual value for the cursor parameter by explaining that the index counts rows rather than positions, eliminating page numbers and arithmetic. This goes beyond the schema's description.

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 Machine captures of a web page with dates, oldest first. It explicitly distinguishes itself from get_snapshot, making its purpose unmistakable.

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

Usage Guidelines5/5

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

It provides explicit when-to-use guidance (answers how long a page has been archived and how often) and names get_snapshot as an alternative it cannot replace. It also explains pagination usage via cursor and warns about slowness, setting clear expectations.

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/smeet666/mcp-archiveorg'

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