Skip to main content
Glama
Upload-Post

Upload-Post

Official

Manage YouTube videos

manage_youtube_videos
Destructive

Manage per-video YouTube settings: rate videos, set thumbnails, and upload, update, or delete captions; preview changes and confirm before sending.

Instructions

Per-video actions on the connected channel (edit title, description, tags, privacy and translations with edit_post). rate (video_id, rating like|dislike|none); set_thumbnail (video_id, thumbnail_url); captions: upload_caption (video_id, file_url, language, name, is_draft; 400+ units, more than a free plan's whole day), update_caption (caption_id, file_url and/or is_draft false to publish a draft; replacing the file needs confirm), delete_caption (caption_id, 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_videos"
  }
}

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.
video_idNorate / set_thumbnail / upload_caption: the video.
confirmedNoSet to true only after the user has seen the preview this tool returns without it and approved it. Without it nothing is sent.
caption_idNoupdate_caption / delete_caption: the track id from youtube_read captions.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.25.0

TDQS

A4.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the risk profile is partly covered, but the description adds real value beyond them: unit costs per action, the daily allowance and midnight-Pacific reset, the 'nothing is sent' preview, and the confirm requirement for irreversible changes. It does not describe the shape of the preview response, though the output schema covers returns.

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?

It is dense and front-loaded with no filler, but the single paragraph packs actions, quota, and approval flow together; light structure (grouping actions vs. quota vs. approval) would make it faster to scan. Every sentence still earns its place.

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?

For a multi-action tool with an opaque params object and a required approval gate, the description covers action fields, quota economics, confirm semantics, and the preview workflow. With an output schema present, return values need not be explained, leaving nothing essential missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema's `params` object is opaque (additionalProperties), and the description compensates by listing each action's fields with meaning: rating values like|dislike|none, is_draft semantics, 'file_url and/or is_draft false to publish a draft', and which actions require confirm. That is substantial meaning beyond the 86%-covered schema.

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 a concrete resource ('per-video actions on the connected channel') and enumerates the exact actions it performs: rate, set_thumbnail, upload_caption, update_caption, delete_caption. It also explicitly routes metadata editing to the sibling edit_post, so an agent can separate this tool from its neighbors without opening a schema.

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

Usage Guidelines5/5

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

It states when to use each action and when to go elsewhere: title/description/tags/privacy/translations belong to edit_post, caption ids come from youtube_read, quota comes from youtube_read quota. It also gives operational guidance (batch reads, avoid needless writes) and the mandatory preview-then-confirm approval sequence.

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