Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_preflight_update_channel

Destructive

Preview channel profile edits by comparing current and desired description, keywords, country, and default language before applying changes while preserving other branding settings.

Instructions

Preview an edit to the selected creator channel profile (description, keywords, country, defaultLanguage), showing current vs desired. Other branding settings are preserved on execute.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "youtube_preflight_update_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoTwo-letter ISO 3166-1 country code of the channel, e.g. US.
keywordsNoNew channel keywords as one string, up to 500 characters.
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. Changed4 schema fields changedv0.3.1
    • 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

A3.6/5.0
Behavior1/5

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

The description frames this as a non-mutating preview ('Preview an edit ... showing current vs desired'), while the annotation declares destructiveHint=true. A preview should not be destructive, so the description directly contradicts the structured safety signal, leaving the agent unsure whether calling this tool mutates data.

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?

Two sentences, front-loaded with the preview purpose, then the preservation guarantee. No wasted words.

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

Completeness4/5

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

For a preflight tool with full schema coverage and no output schema, the description explains what is previewed (current vs desired) and what is preserved on execute. It falls short only by not explicitly naming the paired execute tool or clarifying the destructiveHint discrepancy.

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?

Schema description coverage is 100%, so the schema already documents all four parameters and their constraints. The description adds only a list of the same field names and the preview comparison behavior, not additional syntax or format details beyond the schema. 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 states a specific verb ('Preview an edit') and resource ('selected creator channel profile') and lists the exact editable fields. It clearly separates itself from the sibling youtube_update_channel by being a preview rather than the actual update.

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?

It implies the tool is used before an execute step ('Other branding settings are preserved on execute') but never names youtube_update_channel or explicitly says when not to use this preview. The context is clear enough for an agent to infer the workflow, but explicit routing is missing.

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