Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_create_playlist

Destructive

Create a playlist after approval by providing a title, description, and privacy status, ensuring controlled changes to a YouTube channel.

Instructions

Create an approved creator 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": {
      "title": "<title>",
      "approvalId": "<approvalId>"
    },
    "name": "youtube_create_playlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesTitle of the new playlist, 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_create_playlist preview, after approving it with youtube_approve.
descriptionNoPlaylist description, up to 5000 characters.
privacyStatusNoPlaylist visibility: private, unlisted or public.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.1
    • addedInput schema / properties / approvalId / description
      Added value: +"Approval ID from the youtube_preflight_create_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 / privacyStatus / description
      Added value: +"Playlist visibility: private, unlisted or public."
    • addedInput schema / properties / title / description
      Added value: +"Title of the new playlist, up to 150 characters."
  2. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations declare only destructiveHint=true; the description never warns that this creates a persistent object, that it will fail without a valid approvalId/confirm=true, or what permissions are needed. The word "approved" faintly gestures at the approval gate but explains none of its consequences.

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?

A single front-loaded sentence with no filler. It is efficient, though its brevity is closer to under-specification than to well-edited concision.

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?

For a destructive, approval-gated mutation with no output schema, the description omits the workflow an agent must follow and any indication of what happens on success or failure. The schema partially compensates, but the definition as a whole leaves too much to inference.

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% and the parameter descriptions are unusually rich, covering title length, privacy enum, and the approvalId/confirm workflow. The description adds no parameter meaning of its own, so the 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?

"Create ... playlist" gives a clear verb and resource, but the modifier "approved creator playlist" is ambiguous — it does not clarify that this is a write paired with youtube_preflight_create_playlist, nor distinguish it from that sibling. An agent can guess it creates a playlist but cannot tell from the description alone what "approved" gates.

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?

There is no statement of when to call this versus youtube_preflight_create_playlist, youtube_update_playlist, or youtube_list_playlists. The required preflight → youtube_approve → create sequence is documented only inside the schema's parameter descriptions, not in the tool description itself.

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