Skip to main content
Glama
tubearchivist-mcp

tubearchivist-mcp

by si-essence

ta_download

Destructive

Read and modify the Tube Archivist download queue: list, add, prioritize, start, update, or delete items. Writes run only with confirm=true and writes enabled; otherwise calls preview as dry-run.

Instructions

Read and change the download queue, including add, priority start, and delete. 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/download/), add (POST /api/download/), bulk_update (PATCH /api/download/), bulk_delete (DELETE /api/download/), aggs (GET /api/download/aggs/), get (GET /api/download/{video_id}/), update (POST /api/download/{video_id}/), delete (DELETE /api/download/{video_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": {
      "action": "<action>"
    },
    "name": "ta_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoq
flatNoflat
pageNopage
errorNoerror
forceNoforce
actionYesTube Archivist operation to call.
filterNofilter
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
vid_typeNovid_type
video_idNovideo_id
autostartNoautostart

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds substantial context beyond them: the two-part write gate, the fact that unconfirmed calls send no HTTP write at all, and a per-action mapping of which HTTP verb is used. This is exactly the behavioral detail an agent needs to avoid an unintended destructive call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the purpose, then the critical write-safety rule, then the action catalog. The endpoint list is dense but each entry carries distinct information an agent can act on; no filler sentences.

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 13-parameter, destructive, open-world tool this covers safety and action dispatch well, but it never explains per-action parameter requirements (e.g. that get/update/delete need video_id, or what the `document` object holds for add/update). With no output schema, it also says nothing about what a dry-run response versus a real write returns.

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 nominally 100%, but most field descriptions merely restate the field name (q, flat, page, filter, channel, vid_type, autostart), so the baseline is 3. The description earns an extra point by mapping each action enum value to a concrete HTTP method and endpoint, clarifying which actions are writes (POST/PATCH/DELETE) versus reads (GET); it still leaves ambiguous which parameters pair with which action.

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?

States a specific verb and resource ('Read and change the download queue') and enumerates every supported action with its HTTP method and path, which lets an agent distinguish this tool from siblings like ta_video or ta_library without opening the schema. Minor wrinkle: 'priority start' is mentioned in prose but has no matching enum value (closest is bulk_update), a small inconsistency in an otherwise precise statement.

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?

Gives an explicit operational rule for when a call actually mutates state: confirm must be true AND TUBEARCHIVIST_ALLOW_WRITES=true, otherwise it is a dry-run. That is strong when-to-use guidance, but it offers no guidance on choosing this tool over siblings or on which read actions (list vs get vs aggs) to prefer for a given question.

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