Skip to main content
Glama

youtube_update_video

Destructive

Update title, description, privacy, or tags on a YouTube video. Costs 1600 quota units. Only fields provided are changed.

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": "youtube_update_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoNew tags list. Omit to keep current.
titleNoNew title (max 100 chars). Omit to keep current.
privacyNo'private', 'unlisted', or 'public'. Omit to keep current.
video_idYesBare videoId OR 'youtube:video:<id>'.
account_idNoWhich connected YouTube channel to act as (id from channels.list). OMIT when the workspace has one; with several the call is refused and lists them.
descriptionNoNew description (max 5000 chars). Omit to keep current.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / account_id
      Added value: +{
      +  "description": "Which connected YouTube channel to act as (id from channels.list). OMIT when the workspace has one; with several the call is refused and lists them.",
      +  "type": "integer"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  3. Added
  4. Removed
  5. Added

TDQS

A4.2/5.0
Behavior4/5

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

The description adds useful behavior beyond the annotations by disclosing a 1600 quota-unit cost and clarifying partial-update semantics. The annotations already declare destructiveHint=true and openWorldHint=true, so the description is not required to repeat those safety traits, though it could have noted what destruction or validation risks to expect.

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 description is three short sentences and is front-loaded with the core action. Every sentence contributes useful information: the updatable fields, the quota cost, and the partial-update rule.

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 moderately complex mutation tool, the definition is largely complete: the schema is fully described and annotations carry the destructive/open-world profile. The only minor gap is that the return behavior is not described, and no explicit failure or permission behavior is mentioned.

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 all parameters are already documented in the schema, including account_id and in_workspace. The description only restates the updatable fields and the omit-to-keep behavior already present in the schema, so it adds little parameter meaning beyond the structured data.

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 and resource — updating a YouTube video — and names the exact fields affected: title, description, privacy, and tags. This clearly distinguishes it from sibling tools such as youtube_delete_video and youtube_video_query.

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 gives clear context for use by stating that only fields provided are changed, which tells the agent this is a partial update. It does not explicitly name alternatives or when-not-to-use conditions, but the mutation intent is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.