Skip to main content
Glama
tuitamogamer-gpt

youtube-mcp-server

Add Video to Playlist

youtube_add_video_to_playlist

Add a video to a YouTube playlist by providing playlist and video IDs, with an optional insertion position.

Instructions

Add a YouTube video to one of your playlists, with optional position.

Args

  • playlistId (string, required): The target playlist ID.

  • videoId (string, required): The video ID to add.

  • position (integer ≥ 0, optional): Zero-based position to insert at. If omitted, appends to end.

Returns Confirmation Markdown + structured new playlist item resource:

{
  "playlistItemId": "...",
  "playlistId": "PL...",
  "videoId": "...",
  "position": 0
}

Examples

  • youtube_add_video_to_playlist({ playlistId: "PL...", videoId: "dQw4w9WgXcQ" })

  • Add at position 0: youtube_add_video_to_playlist({ playlistId: "PL...", videoId: "...", position: 0 })

Errors

  • 404 → playlist or video not found.

  • 403 → not your playlist or quota exceeded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
playlistIdYesPlaylist ID to add the video to.
videoIdYesVideo ID to add to the playlist.
positionNoZero-based insertion position. Omit to append at the end.
Behavior4/5

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

Annotations indicate a mutation (readOnlyHint=false). Description expands on behavior with return format, error cases (404, 403), and position details. No contradictions with 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?

Well-organized with headings (Args, Returns, Examples, Errors). Every sentence is informative, no redundancy. Efficient and easy to parse.

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?

Despite no output schema, the description includes the return JSON structure and common errors. It is nearly complete, though it could mention prerequisites like video visibility.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds significant value: clarifies position as zero-based, optional with append behavior, and provides concrete examples. Exceeds baseline.

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?

Clearly states 'Add a YouTube video to one of your playlists, with optional position.' Verb and resource are specific, and the tool is distinct from siblings like `youtube_remove_playlist_item`.

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?

No explicit guidance on when to use this tool versus alternatives. Examples and errors are provided, but there is no direct statement about typical use cases or when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tuitamogamer-gpt/youtube-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server