Skip to main content
Glama
smeet666

mcp-archiveorg

List captures of a page

list_snapshots
Read-onlyIdempotent

List Wayback Machine captures of a web page in chronological order with dates, showing archiving history and frequency. Paginate with cursor for older entries.

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. A capture whose content repeats the row before it is left out of the index answer. The index also holds one site under several addresses at once, such as its www form, its https form and a form carrying credentials, and returns them interleaved, so two consecutive rows can differ because the address differs rather than because the page did. Every row names the address it captured; read that before counting the captures of any one of them. 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?

The description adds extensive behavior beyond the read-only annotations: deduplication of repeated captures, interleaving of multiple site addresses, the difference between capture date and change date, and the row-based index count. It also discloses the performance characteristic ('tens of seconds') and pagination mechanics. No contradiction with 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?

Although lengthy, every sentence carries critical caveats. It is front-loaded with a clear one-sentence purpose followed by well-organized behavioral details. The density of information is high, and the structure supports easy scanning.

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, deduplication, multi-address handling, and interpretation of capture dates—the description covers all essential caveats. An output schema exists, so return fields are not needed. It also sets performance expectations, making the description complete for correct invocation.

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% for all three parameters, so the baseline is 3. The description adds extra meaning about cursor usage ('pass the next_cursor from the previous answer') and clarifies the pagination model ('rows rather than positions, so there is no page number and no arithmetic to do'), which goes beyond the schema descriptions.

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 opens with a specific verb and resource: 'List Wayback Machine captures of a web page, oldest first, with the dates they were taken.' It explicitly differentiates from the sibling get_snapshot: 'Answers how long a page has been archived and how often, which get_snapshot cannot.' This makes the purpose unmistakable and distinct.

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 gives explicit when-to-use guidance by contrasting with get_snapshot and advises on the tool's slowness: 'This route is slow, tens of seconds on a heavily archived address.' It also explains how to paginate with the cursor, so the agent knows exactly when to use this tool and how to proceed.

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