Skip to main content
Glama
tubearchivist-mcp

tubearchivist-mcp

by si-essence

ta_maintenance

Destructive

Preview or perform Tube Archivist maintenance: create/restore snapshots and ZIP backups, rescan files, or import manually; writes require confirm and writes enabled.

Instructions

Snapshots, zip backups, filesystem rescan, and manual import. Writes run only when confirm is true and TUBEARCHIVIST_ALLOW_WRITES=true. Otherwise the call is a dry-run and no HTTP write is sent. Actions: snapshots (GET /api/appsettings/snapshot/), snapshot_create (POST /api/appsettings/snapshot/), snapshot_get (GET /api/appsettings/snapshot/{snapshot_id}/), snapshot_restore (POST /api/appsettings/snapshot/{snapshot_id}/), snapshot_delete (DELETE /api/appsettings/snapshot/{snapshot_id}/), backups (GET /api/appsettings/backup/), backup_create (POST /api/appsettings/backup/), backup_get (GET /api/appsettings/backup/{filename}/), backup_restore (POST /api/appsettings/backup/{filename}/), backup_delete (DELETE /api/appsettings/backup/{filename}/), rescan (POST /api/appsettings/rescan-filesystem/), import (POST /api/appsettings/manual-import/).

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": {
      "action": "<action>"
    },
    "name": "ta_maintenance"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesTube Archivist operation to call.
confirmNoBoolean true runs the write when TUBEARCHIVIST_ALLOW_WRITES is true. Omit it or pass false for a dry-run preview that sends nothing. The string true is rejected.
documentNodocument
filenameNofilename
snapshot_idNosnapshot_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior5/5

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

The annotations only say destructive and non-read-only; the description goes much further by disclosing the two-condition write gate (confirm true AND TUBEARCHIVIST_ALLOW_WRITES=true) and that the fallback is a silent no-op dry-run that sends no HTTP request. That is exactly the kind of hidden precondition an agent would otherwise trip on, especially since a dry-run looks like success.

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-loads the safety-critical write gate before the action catalog, which is the right ordering, and every action entry carries a unique endpoint so none are pure filler. The single dense paragraph with twelve inline entries is harder to scan than a list, and no sentence is wasted but the formatting is not optimized.

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?

No output schema exists, and the description says nothing about what any action returns, whether snapshots come back as IDs, what a backup listing contains, or whether import returns a report. It is adequate on the mechanics but needs to cover response shapes and per-action parameter applicability for a twelve-action destructive tool.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description earns more by decoding the action enum into concrete endpoint semantics, which tells the agent that snapshot_get/delete need snapshot_id and backup_get/restore/delete need filename. It does not clarify the nested 'document' object or state which parameters are ignored for which action, leaving a small 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 definition enumerates the four resource families (snapshots, zip backups, filesystem rescan, manual import) and maps every action to its exact HTTP endpoint, so the agent can tell precisely what this tool touches. It loses a point only because the leading sentence is a noun fragment rather than a verb+object statement, and it never explicitly contrasts itself with ta_config or ta_system, which sit closest to this domain.

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

Usage Guidelines3/5

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

The confirm/TUBEARCHIVIST_ALLOW_WRITES gate gives real operational guidance about when a write will actually take effect versus previewing as a dry-run. However, there is no advice on choosing between sibling tools (ta_config, ta_system, ta_task) or on which of the twelve actions fits a given user intent, so routing decisions still fall to inference.

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