Skip to main content
Glama
tubearchivist-mcp

tubearchivist-mcp

by si-essence

ta_video

Destructive

Read, list, delete, navigate, or comment on archived videos and manage playback progress. Write actions run only with confirm true and writes enabled; otherwise they return a dry-run preview.

Instructions

List, read, delete, navigate, and comment on archived videos, plus playback progress. 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: list (GET /api/video/), get (GET /api/video/{video_id}/), delete (DELETE /api/video/{video_id}/), nav (GET /api/video/{video_id}/nav/), similar (GET /api/video/{video_id}/similar/), comments (GET /api/video/{video_id}/comment/), progress_set (POST /api/video/{video_id}/progress/), progress_clear (DELETE /api/video/{video_id}/progress/).

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

Input Schema

NameRequiredDescriptionDefault
pageNopage
sortNosort
typeNotype
orderNoorder
watchNowatch
actionYesTube Archivist operation to call.
heightNoheight
channelNochannel
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
playlistNoplaylist
video_idNovideo_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already flag destructive=true, readOnly=false and openWorld=true, but the description adds the crucial non-structured fact that every mutation is gated behind a two-part confirmation (confirm=true plus an environment flag) and degrades to a no-op dry-run otherwise. That is exactly the kind of behavior an agent cannot infer from annotations or schema and must know before issuing a delete.

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?

The definition is front-loaded: capability summary first, then the write-safety rule, then the action-to-endpoint table. It is dense but every sentence carries information, with only mild redundancy between the confirm rule in prose and the confirm description in the schema.

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 12-parameter tool spanning eight distinct operations with no output schema, the description is complete on safety and action routing but silent on which of the eight filter/body parameters apply to which action, leaving the agent to guess that document pairs with progress_set or watch with list. It is minimum viable rather than fully sufficient.

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 baseline is 3, and most parameter descriptions (page, sort, type, order, watch, channel, height, playlist, document) are tautological placeholders that the prose does not compensate for. The one genuine addition is expanding the action enum into concrete operations, which is meaningful beyond the bare enumeration, but no parameter-to-action mapping is given.

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

Purpose5/5

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

The description opens with a specific verb set and resource (archived videos plus playback progress) and then enumerates all eight actions with their endpoints, so an agent can tell exactly which capability each call reaches. It is clearly distinguishable from siblings such as ta_search or ta_media because it names the video-scoped resources (nav, similar, comments, progress).

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

Usage Guidelines4/5

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

The write gate is stated explicitly: writes run only when confirm is true and TUBEARCHIVIST_ALLOW_WRITES=true, otherwise the call is a dry-run with no HTTP write. The action list also implicitly routes between list vs get vs delete vs progress_set. What is missing is guidance on when to reach for this tool versus sibling tools like ta_search for lookup or ta_media, and which parameters belong to which action.

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