Skip to main content
Glama
YouTube Playlist MCP

YouTube Playlist MCP

by haktanonur

Add videos to a playlist

add_videos_to_playlist
Idempotent

Adds videos to an existing user-owned playlist, skipping any already present. Requires explicit approval before writing to the account.

Instructions

Add videos to an existing playlist owned by the user; videos already in it are skipped. WRITES TO THE USER'S ACCOUNT: only after explicit approval. Costs 50 units per added video.

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": {
      "playlist_id": "<playlist_id>",
      "video_ids": "<video_ids>",
      "confirm": "<confirm>"
    },
    "name": "add_videos_to_playlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true. Only set it after the user explicitly approved this exact change in the chat.
video_idsYes
playlist_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, idempotentHint=true, destructiveHint=false; the description adds what they cannot: that it writes to the user's account, requires explicit approval, and costs 50 units per added video. The "already in it are skipped" note also explains in plain language why the idempotency hint holds.

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 short sentences, each doing distinct work: purpose, write-risk/approval gate, cost. The safety-critical warning is capitalized and front-loaded mid-description, so nothing is buried.

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 three-parameter write tool with no output schema, the approval gate, cost, and duplicate behavior cover what an agent needs to act safely. It stops short of describing the result (how many were added vs skipped, or errors on invalid IDs), which would matter for reporting back to the user.

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 only 33% (only confirm is documented), so the description carries extra weight and does clarify that playlist_id must be an existing user-owned playlist and video_ids are video identifiers. However, it says nothing about the 50-item cap, the 11-character ID format, or the all-or-nothing vs partial-add behavior, leaving real gaps.

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?

"Add videos to an existing playlist owned by the user" gives a specific verb, resource, and scope constraint (existing, user-owned), which implicitly separates it from create_playlist and remove_videos_from_playlist. The duplicate-skipping clause further pins down the exact operation.

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?

It supplies one hard gating condition (explicit user approval before writing), but never names an alternative such as preview_playlist or get_playlist_items, nor says when this is preferable to creating a new playlist. Usage context is implied rather than routed.

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