Skip to main content
Glama
tuitamogamer-gpt

youtube-mcp-server

Update Video Metadata

youtube_update_video

Update video metadata by merging new title, description, tags, category, privacy, and more. Fetches current data to ensure required fields are always present.

Instructions

Update the metadata of an existing video.

Fetches the current video (snippet + status) first, merges your provided fields, then calls videos.update. This ensures snippet.title and snippet.categoryId (both required by the API) are always present even if you only change one field.

Args

  • videoId (string, required): video to update

  • title (string, optional): new title

  • description (string, optional): new description

  • tags (string[], optional): full replacement tag list

  • categoryId (string, optional): numeric category ID (use youtube_list_video_categories)

  • privacyStatus ("public"|"unlisted"|"private", optional)

  • madeForKids (boolean, optional): sets status.selfDeclaredMadeForKids

  • embeddable (boolean, optional)

  • publicStatsViewable (boolean, optional)

  • defaultLanguage (string, optional): BCP-47 language code

Returns Short confirmation markdown + full updated video resource as structuredContent.

Examples

  • Update title: { "videoId": "abc123", "title": "New Title" }

  • Make private: { "videoId": "abc123", "privacyStatus": "private" }

Errors

  • 400: required fields invalid

  • 403: not your video or scope missing

  • 404: video not found

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
videoIdYesID of the video to update.
titleNoNew video title.
descriptionNoNew video description.
tagsNoFull replacement tag list (replaces all existing tags).
categoryIdNoNumeric video category ID (see youtube_list_video_categories).
privacyStatusNoNew privacy status.
madeForKidsNoMark video as made for kids (sets selfDeclaredMadeForKids).
embeddableNoAllow embedding on external sites.
publicStatsViewableNoAllow public to see extended stats.
defaultLanguageNoBCP-47 default language code (e.g. 'en').
Behavior5/5

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

Annotations are consistent; description details the fetch-then-merge behavior, ensuring required fields are always present, which adds 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear sections (description, args, returns, examples, errors). Information is front-loaded and every sentence is useful.

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: parameters, return format, error codes, and cross-reference. Adequate for a complex tool without output schema.

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

Parameters4/5

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

Input schema covers all parameters (100%), but description adds context like merge behavior, cross-reference to categories tool, and examples, enhancing understanding.

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 'Update the metadata of an existing video' with specific verb and resource. It distinguishes from siblings like upload_video, delete_video, 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?

It explains the merge process, required fields, and gives examples, but does not explicitly state when not to use this tool (e.g., use youtube_get_video to read).

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