Skip to main content
Glama
Upload-Post

Upload-Post

Official

Manage the YouTube channel

manage_youtube_channel
Destructive

Update and organize settings, sections, banners, watermarks, and subscriptions for a connected YouTube channel with preview-before-approval and quota-aware actions.

Instructions

Settings of the connected channel. update (description, keywords, country, default_language, unsubscribed_trailer, localizations {lang: {title, description}}, localizations_remove; only what you send changes; the channel name cannot be changed here); channel page sections: create_section (type, title, playlists, channels, position 0-9), update_section / delete_section (section_id; delete needs confirm); set_banner (image_url); set_watermark (image_url, timing_type, offset_ms, duration_ms; needs confirm), remove_watermark (needs confirm); subscribe (channel_id) and unsubscribe (subscription_id from youtube_read subscriptions). 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_channel"
  }
}

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.
confirmedNoSet to true only after the user has seen the preview this tool returns without it and approved it. Without it nothing is sent.
section_idNoupdate_section / delete_section: the section.
subscription_idNounsubscribe: the subscription id.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.25.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare destructive/openWorld/not-readOnly; the description goes much further by disclosing the two-stage preview-and-confirm protocol, the fact that a preview sends nothing, that deletes and watermark changes need a separate `confirm`, and that the preview is not reversible once confirmed. It also quantifies the real side effect most agents would miss: every call spends the account's daily YouTube allowance, with unit costs (1 read, ~50 writes, 400-450 captions) and the midnight-Pacific reset.

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 front-loaded with the resource, then actions, then cost, then the approval protocol, and essentially every clause carries load-bearing information. The density works against it: the action inventory is one long semicolon-chained block with nested parentheses, which is harder to scan than a short bulleted mapping would be.

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 nine-action multiplexed mutation tool this covers everything the agent needs before calling: valid actions, per-action fields, which changes are irreversible, the approval flow, and the quota economics. Return values are covered by the output schema, so the description correctly does not spend words on them.

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?

Schema coverage is already high at 86%, yet the description still adds substantial meaning: it maps each action to its own params object fields, documents the nested localizations shape ({lang: {title, description}}) plus localizations_remove, lists watermark timing_type/offset_ms/duration_ms, and explains that `confirmed` is the preview gate while `confirm` is the API-level irreversible-change gate — a distinction the schema alone leaves ambiguous.

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 states the resource (the connected channel's settings) and then enumerates each action with its own verb and field set — update, create_section, update_section/delete_section, set_banner, set_watermark/remove_watermark, subscribe/unsubscribe. It also draws the boundary against youtube_read (subscription ids sourced from it, quota visible there), so an agent can separate configuration writes from reads without opening either 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 gives explicit when-to-do-what rules: 'only what you send changes', 'the channel name cannot be changed here', position range 0-9, and where subscription_id comes from. The approval protocol is spelled out operationally — call first without `confirmed` to get a preview, show the user exactly what will go out, then repeat with `confirmed: true` — and it adds cross-call advice to batch reads and avoid needless writes.

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