Skip to main content
Glama
tuitamogamer-gpt

youtube-mcp-server

by tuitamogamer-gpt
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Update Channel Branding

youtube_update_channel_branding

Update your YouTube channel's branding settings including description, keywords, country, language, and unsubscribed trailer. Omitted fields remain unchanged.

Instructions

Update one or more branding fields on the authenticated user's YouTube channel. At least one field must be supplied. The current branding is fetched first and merged, so omitted fields are preserved.

Args (all optional, but at least one required):

  • description (optional): Channel description text (max ~1000 chars visible in branding settings).

  • keywords (optional): Space-separated or quoted keywords for the channel, e.g. "coding tutorial javascript".

  • country (optional): ISO 3166-1 alpha-2 country code, e.g. "US", "GB".

  • defaultLanguage (optional): BCP-47 language code, e.g. "en", "fr".

  • unsubscribedTrailer (optional): Video ID to use as the channel trailer for unsubscribed visitors.

Returns (JSON shape):

{
  "id": "UCxxxxxxxx",
  "brandingSettings": {
    "channel": { "description", "keywords", "country", "defaultLanguage", "unsubscribedTrailer" }
  }
}

Examples:

  • "Set my channel country to GB and keywords to 'gaming commentary'" → pass country: "GB", keywords: "gaming commentary".

  • "Change my trailer video to dQw4w9WgXcQ" → pass unsubscribedTrailer: "dQw4w9WgXcQ".

Errors:

  • 400: invalid field value (e.g. unsupported country code or language tag).

  • 401 / 403: insufficient scope or expired credentials — re-run npm run auth.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionNoChannel description displayed in branding settings.
keywordsNoSpace-separated or quoted keywords for the channel, e.g. "coding tutorial javascript".
countryNoISO 3166-1 alpha-2 country code, e.g. "US", "GB", "DE".
defaultLanguageNoBCP-47 language code for the channel's primary language, e.g. "en", "fr".
unsubscribedTrailerNoVideo ID to show as the trailer to unsubscribed visitors.

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

Describes merge behavior (fetches current branding, merges, omitted fields preserved). Lists error codes (400, 401/403). No contradiction with annotations (readOnlyHint false, destructiveHint false). Adds significant value beyond annotations.

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?

Well-structured with summary, parameter list, return shape, examples, errors. Every sentence is useful. Slightly long but justified by thoroughness.

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?

Covers all aspects: purpose, parameters, merge behavior, return shape, examples, errors. No output schema but return shape provided. Complete for a mutation tool with 5 optional params.

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 100%, but description adds usage details for each parameter (e.g., max chars for description, format for keywords, examples). Adds meaning beyond 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?

Clearly states 'Update one or more branding fields on the authenticated user's YouTube channel'. The verb 'update' and resource 'channel branding' are explicit. Distinguishes from sibling tools which focus on videos, playlists, comments, etc.

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?

States that at least one field must be supplied and explains merge behavior. No explicit 'when not to use' but the tool name and sibling context make the scope clear. Adequate guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tuitamogamer-gpt/youtube-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server