Skip to main content
Glama
tubearchivist-mcp

tubearchivist-mcp

by si-essence

ta_library

Destructive

Refresh reindex status, trigger reindexing, or update watched state for videos, channels, and playlists; writes require confirm=true and allow-writes, otherwise calls preview as dry runs.

Instructions

Reindex progress and watched-state changes for a video, channel, or playlist. 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: refresh_status (GET /api/refresh/), refresh (POST /api/refresh/), watched (POST /api/watched/).

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_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoid
typeNotype
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
extract_videosNoextract_videos

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds meaningful context beyond them: writes only fire when confirm is true AND TUBEARCHIVIST_ALLOW_WRITES=true, otherwise the call is a dry-run that sends no HTTP write. It also distinguishes the read action (GET refresh_status) from the two POST actions. It stops short of 5 because it doesn't say what refresh actually reindexes or destroys, or which objects watched mutates.

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?

Three tightly packed sentences: purpose first, then the critical write-gating rule, then the action enumeration. No filler, though the endpoint notation makes the final sentence dense.

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 six-parameter tool with a nested free-form document object and no output schema, the description covers actions and write safety well but leaves document and extract_videos entirely unexplained, and gives no hint at the return payload for the GET action. Adequate but with clear gaps.

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 coverage is 100%, so the schema already carries the parameter meaning, including a detailed confirm description. The description adds the action-to-endpoint mapping, which clarifies the enum values, but says nothing about id, type, document, or extract_videos. Baseline 3 is appropriate.

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?

Opens with a specific verb+resource statement ('reindex progress and watched-state changes for a video, channel, or playlist') and then enumerates the three callable actions with their HTTP endpoints, so an agent knows exactly what this tool covers. It does not explicitly separate itself from siblings like ta_video or ta_channel, which is the only reason it stops short of a 5.

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 description makes the write/dry-run decision rule explicit, which tells the agent how to call it safely, and the action list implies which operation to pick. However, it never says when to reach for this tool versus a sibling such as ta_video or ta_maintenance, so alternatives are left to inference.

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