ytmcp

update_video_metadata

Edit an existing YouTube video's title, description, tags, category, or language by ID. Update video metadata to keep content accurate and searchable.

Instructions

Update the metadata of an existing video.

Args: video_id: The YouTube video id to edit. title: New title (optional). description: New description (optional). tags: New tag list (optional). category_id: New category id (optional). default_language: New default language code, e.g. 'en' (optional).

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": {
      "video_id": "<video_id>"
    },
    "name": "update_video_metadata"
  }
}

Input Schema

Name	Required	Description	Default
`tags`	No
`title`	No
`video_id`	Yes
`category_id`	No
`description`	No
`default_language`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 1, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations at all, so the description carries the full burden and largely drops it. It never states that this is a mutating operation, whether it requires ownership/OAuth scopes or quota, or that omitted fields are left unchanged. Only the '(optional)' markers hint at partial-update semantics.

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?

One front-loaded sentence states the action, followed by a compact Args list. The Args block slightly duplicates parameter names but is justified given the total absence of schema descriptions.

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

Completeness3/5

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

An output schema exists so return values need not be explained, and all parameters are named. However, for a mutation tool with zero annotations, the description omits auth/quota requirements and exact partial-update behavior, leaving meaningful gaps.

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?

Schema description coverage is 0% and titles are bare ('Video Id', 'Tags'), so the Args block does real work: it identifies video_id as 'The YouTube video id to edit' and gives a format example for default_language ('en'). It covers all six parameters, though tags/category_id get only one-line restatements with no format detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Update the metadata of an existing video'), which clearly separates it from siblings like upload_video, delete_video, and set_video_visibility. It does not explicitly name an alternative, but the purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no prerequisites, no mention of alternatives such as set_video_visibility or upload_video. The agent must infer that this is the tool for editing an existing video's descriptive fields.

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