Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_preflight_create_playlist

Destructive

Preview a YouTube playlist before creation by specifying title, optional description, and visibility; private is the default.

Instructions

Preview creation of a creator playlist; private is the default visibility.

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

Input Schema

NameRequiredDescriptionDefault
titleYesTitle of the new playlist, up to 150 characters.
descriptionNoPlaylist description, up to 5000 characters.
privacyStatusNoPlaylist visibility: private, unlisted or public.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.1
    • 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

B3.3/5.0
Behavior2/5

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

The description frames this as a preview, i.e. a non-mutating validation, while annotations declare destructiveHint=true — the two signals point in opposite directions for an agent assessing risk. Beyond that conflict, the description does not say what a preview returns (validation errors? a token?) or whether any state changes. The one genuine addition is the default visibility value, which is not derivable from annotations.

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 front-loaded sentence with two clauses, each carrying distinct information (dry-run purpose, default visibility). No filler or restatement of the tool name.

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 dry-run/preflight tool with no output schema, the description should explain what the preview produces and how to follow up with the real create call; neither is present. Combined with a destructive annotation that is at odds with the preview framing, an agent lacks what it needs to use this safely in a workflow.

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 a fact the schema lacks: that privacyStatus defaults to private when omitted. That is actionable semantics beyond the enum listing and justifies a step above baseline.

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?

"Preview creation of a creator playlist" gives a specific verb (preview) and resource (playlist), and the preflight framing signals a dry-run rather than a real write. It does not explicitly name youtube_create_playlist as the confirm step, so the sibling distinction is inferable from 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?

"Preview" implies this is a validation step rather than the real creation, which is useful implied guidance. However, it never states when to call it (before youtube_create_playlist?), what a successful preview means, or that youtube_create_playlist is the tool that actually creates the playlist.

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