Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_preflight_update_playlist

Destructive

Preview an update to an owned YouTube playlist, letting you review proposed title, description, or privacy changes before approval.

Instructions

Read and preview an update to an 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>"
    },
    "name": "youtube_preflight_update_playlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoPlaylist title, up to 150 characters.
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. Changed4 schema fields changedv0.3.1
    • 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

B3.1/5.0
Behavior1/5

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

The description characterizes the operation as "read and preview", i.e., non-mutating, while annotations declare destructiveHint=true. An agent cannot reconcile these: either the tool has side effects the description hides, or the annotation overstates risk — in both cases the safety profile conveyed is unreliable.

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?

A single short, front-loaded sentence with zero filler. Nothing is padded or repeated from the schema.

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?

The tool has no output schema, so the description should explain what a "preview" returns (planned diff, validation errors, a token for the follow-up update), and it does not. Combined with unresolved mutation semantics, an agent still lacks what it needs to act on the result.

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 coverage is 100%, with per-field descriptions and length limits plus an enum for privacyStatus, so the baseline of 3 applies. The description adds nothing about partial-update semantics (e.g., whether omitting title/description/privacyStatus leaves them untouched) or how playlistId is scoped to ownership.

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?

"Read and preview an update to an owned playlist" gives a specific verb pair (read/preview) and a specific resource (owned playlist update), which separates it from the mutating sibling youtube_update_playlist in intent. It stops short of naming that sibling, so the distinction must be inferred from the "preflight" naming convention rather than stated.

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

Usage Guidelines3/5

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

Usage is only implied through the "preflight" prefix and the word "preview" — an agent can guess this should precede youtube_update_playlist, but the description never says so, nor does it state whether the preview result is required input for the actual update or what to do if the preview fails.

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