YouTube Playlist MCP

Create playlist on YouTube

create_playlist

Creates an approved playlist draft in the user's YouTube account and adds its videos after explicit confirmation, ensuring writes occur only for the reviewed draft_id.

Instructions

Create the previewed playlist in the user's YouTube account and add its videos. WRITES TO THE USER'S ACCOUNT: call only after the user explicitly approved the preview for this draft_id. Each draft can be created once. Costs 50 + 50 per video quota units.

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": {
      "draft_id": "<draft_id>",
      "confirm": "<confirm>"
    },
    "name": "create_playlist"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	Yes	Must be true. Only set it after the user explicitly approved this exact change in the chat.
`draft_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations it discloses the consequential behavior an agent needs: this writes to the user's real account, requires explicit user approval, is single-use per draft (giving concrete meaning to idempotentHint=false), and costs 50 + 50 per video quota units. That is exactly the extra context annotations cannot carry.

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?

Three tight sentences, with the irreversible-write warning front-loaded before the operational details. No filler and every clause carries decision-relevant information.

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 gated, quota-costed mutation with no output schema, it covers safety, preconditions, and cost. The only gap is that it never indicates what a successful call yields (e.g., the new playlist ID), which the agent would need for follow-up calls.

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 50%: 'confirm' is fully documented in the schema, while 'draft_id' has no schema description. The description partially compensates by tying draft_id to a previewed draft and stating each draft can be created once, but it never says where draft_id comes from or its format.

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 names a specific verb and resource ('Create the previewed playlist... and add its videos') and anchors it to the draft-preview workflow, which clearly separates it from add_videos_to_playlist (which targets an existing playlist). An agent can pick between the two without opening either schema.

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 a hard precondition — only call after the user explicitly approved the preview for this draft_id — plus a single-use rule per draft, which implies preview_playlist must run first. It never names preview_playlist as the source of draft_id explicitly, so the routing is implied rather than spelled out.

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

Deploy Server