ArchiveBox API

Get snapshots rss

archivebox_get_snapshots_rss

Read-onlyIdempotent

Retrieve an RSS feed of recent ArchiveBox snapshots, filtered by crawl, creator, time, or item limit. Use it to monitor new archived pages without manual checks.

Instructions

GET /api/v1/core/snapshots.rss

RSS feed of recent snapshots.

Args: crawl_id: Only snapshots of this crawl. created_by: Only snapshots created by this user. limit: Maximum feed items. before: Only snapshots before this time (ISO 8601).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "archivebox_get_snapshots_rss"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`before`	No
`crawl_id`	No
`created_by`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.6.0Nov 7, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds that the result is an RSS feed of *recent* snapshots, but says nothing about default limit, ordering, or how many items come back when limit is omitted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the endpoint path and a one-sentence purpose, followed by a compact Args block. The raw "GET /api/v1/core/snapshots.rss" line is marginal value for an agent but costs little, and nothing is padded.

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

Completeness3/5

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

With no output schema, the description does convey that the return value is an RSS document, which is the key fact. It omits default page size, sort order, and any auth/token prerequisite, leaving gaps for a four-filter listing endpoint.

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 0%, so the description carries the burden, and it does give a one-line meaning for all four parameters, including the ISO 8601 format hint for `before`. It does not clarify what identifier form crawl_id/created_by take or what limit defaults to, so the compensation is partial.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"RSS feed of recent snapshots" states a specific resource (snapshots) plus output format (RSS), which is enough to tell it apart from archivebox_get_snapshots (which returns structured data). It never names that sibling explicitly, so the differentiation is left partly to inference.

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

Usage Guidelines2/5

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

There is no statement of when to pick this over archivebox_get_snapshots, archivebox_get_tag_snapshots_jsonl, or the crawl/snapshot getters. The only usage signal is the implied "you want a feed" from the word RSS in the name and description.

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

Deploy Server