Skip to main content
Glama
Sign In
youtube-playlists-mcp

youtube-playlists-mcp

by kvechkanov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

add_to_playlist

Append a video to an existing YouTube playlist by providing the playlist ID and video ID or URL; duplicates are not checked.

Instructions

Add a video to a playlist (appended at the end). Quota cost: 50 units per call. Does not check for duplicates.

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

Input Schema

NameRequiredDescriptionDefault
videoYesVideo ID or URL (watch, youtu.be, shorts, embed).
playlistIdYesTarget playlist ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses quota cost (50 units per call), append position, and that no duplicate detection occurs. What is missing is permission/auth requirements and error behavior when the playlist does not exist or is not owned by the caller.

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 front-loaded with a distinct piece of information (action, cost, caveat). Nothing is repeated from the schema and no wording is wasted.

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 simple two-parameter mutation tool with no output schema, the description covers the key operational facts an agent needs: quota cost, append semantics, and duplicate behavior. Return value details are omitted, but since no output schema exists this is a minor gap for a call that primarily succeeds or fails.

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%, including accepted video ID/URL formats, so the schema already does the parameter work. The description adds no parameter semantics beyond noting the item is appended at the end, so the baseline of 3 applies.

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?

The description gives a specific verb and resource ('Add a video to a playlist') plus the placement behavior ('appended at the end'), which distinguishes it from remove_playlist_item and list_playlist_items. It does not name a sibling explicitly, so differentiation comes from the verb rather than an explicit comparison.

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 implied by the verb and the caveat 'Does not check for duplicates' warns the agent about a common pitfall. However, it never states when to prefer this over alternatives such as create_playlist, nor does it mention prerequisites like playlist ownership or where to obtain a video ID (only the schema hints at that).

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