Skip to main content
Glama
tubearchivist-mcp

tubearchivist-mcp

by si-essence

ta_playlist

Destructive

Manage Tube Archivist playlists: list, subscribe, create/update custom playlists, get details, delete. Writes require confirm and allow-writes; otherwise calls preview as dry-runs.

Instructions

List, subscribe, update, and delete playlists, including custom playlists. 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/playlist/), subscribe (POST /api/playlist/), create_custom (POST /api/playlist/custom/), update_custom (POST /api/playlist/custom/{playlist_id}/), get (GET /api/playlist/{playlist_id}/), update (POST /api/playlist/{playlist_id}/), delete (DELETE /api/playlist/{playlist_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_playlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNopage
typeNotype
actionYesTube Archivist operation to call.
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
subscribedNosubscribed
playlist_idNoplaylist_id
delete_videosNodelete_videos

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and readOnlyHint=false, so the safety profile is known. The description adds genuinely useful behavior beyond that: the two-factor write gate and the fact that a non-confirmed call sends no HTTP write at all, so it behaves as a preview. It stops short of describing side effects such as what delete removes (the delete_videos parameter hints at cascade) or permission requirements.

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 write-gating rule is front-loaded in the second sentence where it matters most, and the action/endpoint list is dense but functional. The endpoint enumeration is longer than strictly necessary for an agent that already has an action enum, but it carries real routing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter, destructive, open-world tool with no output schema, the description covers the most consequential unknown: exactly when a write actually fires. Missing pieces such as return shape and per-action parameter applicability are moderate but not disqualifying given full schema coverage.

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 the baseline is 3, and the description earns a step above it by mapping each action value to its endpoint, which lets the agent infer which parameters matter per action (e.g., playlist_id for get/update/delete). It still does not state per-action required or ignored parameters.

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 names the resource (playlists, including custom playlists) and enumerates every supported verb (list, subscribe, create_custom, update_custom, get, update, delete) with the corresponding HTTP endpoint for each. This makes it unmistakably distinct from siblings like ta_video or ta_channel.

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?

It clearly states the condition that gates writes (confirm=true plus TUBEARCHIVIST_ALLOW_WRITES=true) and that otherwise the call is a dry-run, which tells the agent how to safely probe. It does not, however, say when to choose subscribe versus create_custom, or when a playlist operation should be routed to a sibling tool instead.

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