Skip to main content
Glama
thaenor

arquivo-pt-mcp

by thaenor

list_versions

List every archived capture of a URL to see how the page evolved over time. Filter results by date range, status code, mime type, and more.

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 provided; description fails to disclose behavioral traits such as result size limits, rate limiting, or that it queries the Wayback Machine CDX API. 'Every archived capture' suggests potentially huge data without warning.

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?

Extremely concise at two sentences, front-loaded with the core purpose. No superfluous words.

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?

Despite 10 parameters and no output schema, the description is minimal. It does not explain the CDX concept, how filters work, or pagination behavior, leaving an agent underinformed for effective use.

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 90%, so parameters are well-documented in the schema. The tool description adds no additional meaning beyond what the schema already provides, meeting the baseline.

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?

Description clearly identifies the tool as listing archived captures for a URL, with the verb 'list' and resource 'archived captures'. It distinguishes from siblings like get_snapshot by focusing on history and change over time.

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?

Explicitly says 'Use to see how a page changed over time,' giving a clear context. Lacks explicit when-not-to-use or alternatives, but sibling set implies other tools for individual captures or search.

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