Skip to main content
Glama
Upload-Post

Upload-Post

Official

Manage YouTube playlists

manage_youtube_playlists
Destructive

Create, update, or delete YouTube playlists; add, move, or remove videos and set or replace images for a connected channel, with previews before sending.

Instructions

Playlists of the connected channel. create (title, description, privacy_status public|unlisted|private, default_language, localizations); update (playlist_id; only what you send changes, localizations_remove); delete (playlist_id; the videos stay, needs confirm); add_video (playlist_id, video_id, position, note), update_video (playlist_id, item_id: move with position or change note), remove_video (playlist_id, item_id, needs confirm); set_image / replace_image (playlist_id, image_url: square JPEG or PNG; replace needs confirm), delete_image (needs confirm). Every call spends the account's daily YouTube allowance (free plan 200 units, paid plans 2,000; resets at midnight Pacific time; youtube_read quota shows what is left): reads cost about 1 unit, most writes 50, captions 400-450, so batch reads and avoid needless writes. Needs the user's approval: call it first without confirmed to get a preview (nothing is sent), show the user exactly what will go out, and repeat the call with confirmed: true only after they approve.

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>",
      "user": "<user>"
    },
    "name": "manage_youtube_playlists"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYesUpload-Post profile name with YouTube connected.
actionYes
paramsNoOther API fields for this action, with the REST API's own names (snake_case) and shapes. See the description for each action's fields. Leave out what you do not want to change.
confirmNoThe API's own confirmation for deletions and other changes that cannot be undone. Set it to true only after the user has approved that exact change; without it those actions are refused and nothing changes.
item_idNoupdate_video / remove_video: the playlist item id from youtube_read playlist_items (not the video id).
confirmedNoSet to true only after the user has seen the preview this tool returns without it and approved it. Without it nothing is sent.
playlist_idNoThe playlist (every action but create).

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.25.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only flag destructive and open-world; the description adds what actually matters beyond them: delete leaves the videos intact, replace_image/delete_image are irreversible and gated on confirm, every call burns the daily quota with concrete unit costs and the midnight-Pacific reset, and the first call without `confirmed` sends nothing. That is a materially richer behavioral picture than the annotation triple.

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?

Dense but well-organized: resource line first, then a semicolon-delimited action inventory, then quota economics, then the approval protocol. It is long, but for a nine-action multiplexed tool nearly every clause carries information; the action list could have been bulleted for faster scanning.

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

Completeness5/5

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

With an output schema present, return values need no explanation, and the description covers the remaining burdens: action semantics, params shapes, destructive confirmations, quota limits, and the approval loop. Nothing an agent would need in order to call this correctly without a rejected request appears to be missing.

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 86%, so the baseline is 3, but the description goes further by enumerating the per-action field set that belongs in the free-form `params` bag (title, description, privacy_status, default_language, localizations, localizations_remove, position, note) plus image format constraints. That is the only place an agent learns which keys each action accepts, which is essential given the open-ended params object.

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?

Opens with the resource ("Playlists of the connected channel") and then enumerates all nine concrete actions with their required fields, so an agent knows exactly what surface this tool covers. That scope statement distinguishes it from the sibling video/channel/comment managers without needing to open the schema.

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 clear operational guidance: batch reads, avoid needless writes because of quota, and the two-phase confirm-before-send workflow triggered by the user-approval requirement. It also hints that reads live elsewhere (youtube_read playlist_items for item_id, youtube_read quota), but never states explicitly when to pick this tool over youtube_read, which keeps it below 5.

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

Deploy Server

Other Tools