Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_update_playlist

Destructive

Updates an owned YouTube playlist's title, description, or privacy status using an approved preview, so changes apply only after explicit approval and confirmation.

Instructions

Update an approved owned playlist.

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": {
      "playlistId": "<playlistId>",
      "approvalId": "<approvalId>"
    },
    "name": "youtube_update_playlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoPlaylist title, up to 150 characters.
confirmNoMust be true to execute; set it only after youtube_approve approved this exact preview.
approvalIdYesApproval ID from the youtube_preflight_update_playlist preview, after approving it with youtube_approve.
playlistIdYesYouTube playlist ID, e.g. PLxxxxxxxxxxxxxxxx.
descriptionNoPlaylist description, up to 5000 characters.
privacyStatusNoPlaylist visibility: private, unlisted or public.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.3.1
    • addedInput schema / properties / approvalId / description
      Added value: +"Approval ID from the youtube_preflight_update_playlist preview, after approving it with youtube_approve."
    • addedInput schema / properties / confirm / description
      Added value: +"Must be true to execute; set it only after youtube_approve approved this exact preview."
    • addedInput schema / properties / description / description
      Added value: +"Playlist description, up to 5000 characters."
    • addedInput schema / properties / playlistId / description
      Added value: +"YouTube playlist ID, e.g. PLxxxxxxxxxxxxxxxx."
    • addedInput schema / properties / privacyStatus / description
      Added value: +"Playlist visibility: private, unlisted or public."
    • addedInput schema / properties / title / description
      Added value: +"Playlist title, up to 150 characters."
  2. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations declare only destructiveHint=true; the description adds no detail on what is overwritten, whether omitted fields are cleared, or that confirm must be true. The schema carries the confirm/approvalId gating, so the description contributes almost nothing beyond the annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

A single front-loaded sentence with zero waste, but the brevity comes at the cost of under-specification rather than efficient information density.

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

Completeness2/5

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

This is a destructive mutation gated behind an approval workflow with six parameters and no output schema, so the description should explain the preflight→approve→update sequence. Instead it is one short clause that leaves the workflow and mutation consequences to be reconstructed from the schema.

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 six parameters including the approvalId/confirm gating are already documented in the schema. The description adds no syntax or constraint detail beyond what structured data provides; baseline 3 applies.

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

Purpose3/5

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

States the verb (update) and resource (playlist), and adds the qualifier 'approved owned', which hints at the approval-gated flow. But it does not distinguish this from youtube_preflight_update_playlist or youtube_create_playlist, and 'owned' is left unexplained.

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?

'Approved' implies a prerequisite, but the description never names youtube_preflight_update_playlist or youtube_approve, nor states when to use this versus the preflight sibling. The agent must infer the two-step workflow from the schema alone.

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