Skip to main content
Glama
Sign In
ArchiveBox API

ArchiveBox API

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Delete tag

archivebox_delete_tag
DestructiveIdempotent

Deletes an ArchiveBox tag while preserving its snapshots, which remain untagged.

Instructions

DELETE /api/v1/core/tag/{tag_id}

Delete a tag (snapshots keep existing, untagged).

Args: tag_id: Tag 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": {
      "tag_id": "<tag_id>"
    },
    "name": "archivebox_delete_tag"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.6.0

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: deleting a tag does not delete snapshots, they are simply left untagged, which is the key side effect an agent needs to know. It omits permissions, error behavior for a missing tag, and the purpose of the confirm parameter.

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 description is short and front-loads the destructive action, which is good. However, the raw HTTP route line and the redundant 'Args: tag_id: Tag id.' block consume space without adding information the agent needs.

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 simple two-parameter destructive tool with no output schema, the description covers the essential outcome (snapshots preserved but untagged). It leaves out how to obtain a valid tag_id, what happens when the id does not exist, and whether the deletion is recoverable.

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?

With schema coverage at 50%, the description should compensate for the undocumented tag_id, but it only restates 'tag_id: Tag id.' which is tautological and adds no format, source, or lookup guidance (e.g., obtainable via archivebox_search_tags). The confirm parameter, the one the schema does document, is not mentioned at all.

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 states a specific verb and resource ('Delete a tag') plus the endpoint, and it clarifies the scope by noting snapshots survive and become untagged, which distinguishes it from archivebox_delete_snapshot and archivebox_remove_tag_from_snapshot. It stops short of naming an alternative sibling explicitly, so it is clear but not maximally differentiating.

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 use this tool versus archivebox_rename_tag, archivebox_remove_tag_from_snapshot, or archivebox_get_tag. The only guidance-adjacent information is the outcome note about snapshots, which is behavioral rather than a usage rule.

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