Skip to main content
Glama
tubearchivist-mcp

tubearchivist-mcp

by si-essence

ta_channel

Destructive

List, search, subscribe to, update, or delete Tube Archivist channels; write operations require explicit confirmation and otherwise return a dry-run preview.

Instructions

List, search, subscribe, update, and delete channels. 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/channel/), subscribe (POST /api/channel/), search (GET /api/channel/search/), get (GET /api/channel/{channel_id}/), update (POST /api/channel/{channel_id}/), delete (DELETE /api/channel/{channel_id}/), aggs (GET /api/channel/{channel_id}/aggs/), nav (GET /api/channel/{channel_id}/nav/).

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

Input Schema

NameRequiredDescriptionDefault
qNoq
pageNopage
actionYesTube Archivist operation to call.
filterNofilter
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
channel_idNochannel_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, but the description goes beyond them by explaining exactly how write safety works: writes require both confirm=true and the TUBEARCHIVIST_ALLOW_WRITES environment flag, otherwise the call degrades to a dry-run that sends no HTTP write. That is precisely the operational context an agent needs before invoking a destructive multiplexer.

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-loaded with the verb list, then the write-gating rule, then a compact action-to-endpoint map. Almost every clause carries information. The final endpoint list is dense and comma-joined, which slightly hurts scanning but is justified by the eight-action surface.

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 seven-parameter, eight-action dispatcher with a free-form nested object and no output schema, the description covers the action set and the safety model but omits which parameters each action consumes and how pagination (page/q/filter) applies. An agent can pick an action but may still guess at argument combinations, so it is adequate rather than complete.

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 description coverage is 100%, so the schema already documents confirm, q, page, filter and channel_id, and the 3 baseline applies. The description reinforces the confirm semantics but adds no action-level parameter binding, and the nested `document` payload (used presumably by subscribe/update) is left entirely unexplained by both description and schema.

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 opening sentence names the specific resource (channels) and enumerates the operations (list, search, subscribe, update, delete), which lets an agent tell it apart from sibling tools such as ta_video or ta_playlist without reading the schema. The endpoint-per-action list further pins down scope. It stops short of 5 only because it never characterizes what a 'channel' represents here beyond the endpoint paths.

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?

Usage guidance is implied through the action enumeration, and the write gate tells the agent how to actually execute a mutation. However, there is no statement of when to prefer this tool over ta_search or ta_video, and no guidance on which action requires which parameters (e.g. channel_id for get/update/delete/aggs/nav, q for search). An agent must infer the action-to-parameter mapping.

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