Skip to main content
Glama
thaenor

arquivo-pt-mcp

by thaenor

list_versions

Retrieve the archived history of a URL to examine how its content changed over time.

Instructions

List every archived capture of a specific URL (CDX query). Use to see how a page changed over time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to query capture history for
limitNo
offsetNoPagination offset for CDX results (skip first N captures)
compactNoReturn year-bucketed summary instead of full CDX records. Reduces output size for URLs with many captures.
filterNoField filters, repeatable. Format: '=field:value' (exact), '!=field:value' (negate+exact), '~field:regex' (regex), '!~field:regex' (negate+regex). Example: ['=status:200', '=mime:text/html']
match_typeNoURL matching: exact (default), prefix, host, or domainexact
from_dateNoStart timestamp: YYYY, YYYY-MM, YYYY-MM-DD, or YYYYMMDDHHMMSS
to_dateNoEnd timestamp (same format as from_date)
sortNoSort order: default (chronological), reverse (newest first), closest (require 'closest' param)default
closestNoTimestamp for sort=closest to rank by time-distance. Accepts same date formats as from_date.
Behavior2/5

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

No annotations are provided, so the description must carry the burden. It only says 'List every archived capture' and 'CDX query,' which is minimal. It does not disclose pagination, sorting behavior, or what the output looks like, relying heavily on the schema which already provides some detail.

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?

Two sentences with no fluff. The first states the action and resource, the second provides a use case. Front-loaded and efficient.

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?

With 10 parameters and no output schema, the description is too brief. It does not explain return format, pagination, or how to combine parameters for specific queries, leaving the agent to infer from schema alone.

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 high (90%), so baseline is 3. The description adds no parameter-specific meaning; all semantics are deferred to the parameter descriptions in 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 archived captures of a specific URL (CDX query) and provides a use case (seeing how a page changed over time). It distinguishes from siblings like get_snapshot or extract_text by focusing on listing historical versions.

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 explicitly says 'Use to see how a page changed over time,' giving clear context for when to use it. It does not mention when not to use it or compare directly to siblings, but the purpose is well-defined.

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/thaenor/arquivo-pt-mcp'

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