Skip to main content
Glama

youtube_update_channel

Destructive

Apply an approved YouTube channel profile edit, preserving untouched branding fields and requiring confirmation before changes are written.

Instructions

Apply an approved channel profile edit (read-modify-write of brandingSettings so untouched fields are kept). Approve with youtube_approve, then call with confirm: true and the same fields. youtube_my_account shows the snippet description, which can lag the stored branding description for a while.

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": {
      "approvalId": "<approvalId>"
    },
    "name": "youtube_update_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to execute; set it only after youtube_approve approved this exact preview.
countryNoTwo-letter ISO 3166-1 country code of the channel, e.g. US.
keywordsNoNew channel keywords as one string, up to 500 characters.
approvalIdYesApproval ID from the youtube_preflight_update_channel preview, after approving it with youtube_approve.
descriptionNoNew channel description, up to 1000 characters.
defaultLanguageNoDefault language code of the channel, e.g. en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.3.1
    • addedInput schema / properties / approvalId / description
      Added value: +"Approval ID from the youtube_preflight_update_channel preview, after approving it with youtube_approve."
    • addedInput schema / properties / confirm / description
      Added value: +"Must be true to execute; set it only after youtube_approve approved this exact preview."
    • addedInput schema / properties / country / description
      Added value: +"Two-letter ISO 3166-1 country code of the channel, e.g. US."
    • addedInput schema / properties / defaultLanguage / description
      Added value: +"Default language code of the channel, e.g. en."
    • addedInput schema / properties / description / description
      Added value: +"New channel description, up to 1000 characters."
    • addedInput schema / properties / keywords / description
      Added value: +"New channel keywords as one string, up to 500 characters."
  2. Addedv0.3.0

TDQS

A4.7/5.0
Behavior5/5

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

The description discloses critical behavioral traits beyond the `destructiveHint`, specifically that it performs a 'read-modify-write' operation to preserve untouched fields and warns about the eventual synchronization lag observed in youtube_my_account.

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?

The definition is highly concise, using only two sentences to convey a complex, multi-stage operational workflow, making excellent use of front-loading and density.

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?

Given the complexity of the workflow (pre-approval step, data persistence logic, UI lag), the description covers all critical contextual requirements necessary for an agent to use this tool correctly and anticipate system behavior.

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

Parameters3/5

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

With schema description coverage at 100%, the description confirms the scope (brandingSettings) but does not add unique meaning or technical semantics to the individual input parameters beyond what is provided in the input schema definitions. Baseline 3 is appropriate.

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 clearly states the tool's purpose: to apply an approved channel profile edit. It specifies the nature of the operation (read-modify-write of brandingSettings) and what criteria the edit must meet (approved).

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 provides explicit usage guidelines, detailing that the tool is part of a multi-step process involving `youtube_approve` first, and specifies the required input configuration (`confirm: true`). It also warns about the eventual visibility lag on YouTube.

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