Skip to main content
Glama
Sign In
ArchiveBox API

ArchiveBox API

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Delete snapshot

archivebox_delete_snapshot
DestructiveIdempotent

Delete an ArchiveBox snapshot and its archive results by snapshot ID; set confirm when the client cannot handle a destructive-operation prompt.

Instructions

DELETE /api/v1/core/snapshot/{snapshot_id}

Delete one snapshot and its archive results.

Args: snapshot_id: The snapshot id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "snapshot_id": "<snapshot_id>"
    },
    "name": "archivebox_delete_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoExplicitly confirm this destructive operation. Needed only when the client cannot answer a confirmation prompt.
snapshot_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.6.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description contributes the one genuinely new behavioral fact — that archive results are deleted along with the snapshot — but says nothing about irreversibility, the confirmation requirement, or auth needs.

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

Conciseness3/5

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

The prose is short and front-loaded, but the raw HTTP endpoint line and a one-item 'Args' block are boilerplate that mostly restate the schema. Space that could carry behavioral detail is spent on filler.

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?

For a destructive, non-idempotent-looking operation with no output schema, the definition should at least mention the confirm parameter and irreversibility. It covers the cascade deletion, which is valuable, but leaves the agent to infer the confirmation flow from the schema alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%, and the description's sole parameter note ('snapshot_id: The snapshot id') is a tautology that adds no meaning. The more interesting parameter, confirm, is fully explained in the schema but never mentioned in the description, so the description does not compensate for the coverage gap.

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?

The description names a specific verb and resource ('Delete one snapshot') and adds the cascade effect ('and its archive results'), which distinguishes it from siblings like archivebox_delete_crawl or archivebox_delete_tag. The raw 'DELETE /api/v1/core/snapshot/{snapshot_id}' line reinforces the resource but is redundant with the prose.

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 guidance on when to choose this over adjacent tools such as archivebox_cli_remove, archivebox_delete_crawl, or archivebox_patch_snapshot. Nothing states prerequisites (API token, permissions) or when the confirm flag must be supplied, even though the schema implies a confirmation workflow.

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

Deploy Server

Other Tools