Skip to main content
Glama

update_video_details

Destructive

Apply a title, description and/or tags to one of the signed-in user's own YouTube videos. ONLY call this after you have shown the user the exact wording and they have explicitly approved it, the same way you would before posting a comment reply. NEVER write the wording yourself and apply it in one step. Pass only the fields being changed; anything you omit is left exactly as it is. Call it with just video and no other field to see what Klyf has already changed on that video and what the values were before, which is how you put something back. Klyf Pro, and needs the user's one-time write permission; if they lack either it returns the link they need.

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": "<video>"
    },
    "name": "update_video_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoThe complete new tag list the user approved, replacing the existing tags. Omit to leave tags alone; pass an empty array to remove them all. Emit this as an actual JSON array value, NOT as a quoted string containing JSON.
titleNoThe exact new title the user approved. Omit to leave the title alone.
videoYesWhich of the user's videos: its title, or its video id
descriptionNoThe exact new description the user approved. Omit to leave the description alone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, and the description adds substantial context beyond them: partial-update semantics ('anything you omit is left exactly as it is'), a read-back mode that reveals prior values for reverting, and entitlement/permission gating with the fallback return ('it returns the link they need'). This is the kind of behavioral detail an agent needs before performing a destructive write.

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?

Front-loaded with the action, then the approval gate, then the omit/restore semantics and entitlement caveat — a logical order with little waste. It is slightly overpacked, and the sentence 'Klyf Pro, and needs the user's one-time write permission' is grammatically broken (a missing verb), which momentarily obscures the requirement.

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 destructive mutation with no output schema, the description covers approval workflow, partial-update behavior, entitlement requirements, and the failure return path. The one gap is that it never states what a successful write returns or how the agent confirms the change landed.

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 coverage is 100%, so the baseline is 3, but the description adds genuine PATCH semantics ('Pass only the fields being changed; anything you omit is left exactly as it is') and repurposes the `video` parameter as a standalone audit mode. That is meaningful meaning beyond the schema's per-field descriptions.

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?

States a specific verb and resource with clear scope: 'Apply a title, description and/or tags to one of the signed-in user's own YouTube videos.' This cleanly separates it from drafting siblings like draft_description and from reply_to_comment, which the description explicitly contrasts against.

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

Usage Guidelines5/5

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

Gives an explicit precondition ('ONLY call this after you have shown the user the exact wording and they have explicitly approved it'), a negative rule ('NEVER write the wording yourself and apply it in one step'), and a distinct alternate mode ('Call it with just `video` and no other field'). Nothing is left to inference about when this tool is appropriate.

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.

Resources