YouTube Personal Playlist noAPI MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YOUTUBE_COOKIE_FILE | No | Path to the cookies.txt file. If not provided, defaults to $XDG_CONFIG_HOME/youtube-personal-playlist-noapi-mcp/cookies.txt or ~/.config/youtube-personal-playlist-noapi-mcp/cookies.txt. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| youtube_cookie_setB | Store pasted YouTube cookies at the configured cookie path and verify login + playlist access. |
| youtube_cookie_statusA | Show where cookies are stored and test whether the stored cookies currently authenticate. |
| youtube_account_infoB | Get concise account identity for the authenticated YouTube session. |
| youtube_list_playlistsA | List account-visible playlists as compact normalized data. |
| youtube_get_playlistB | Get one playlist page. page is 1-based; use next_page when has_more is true. |
| youtube_create_playlistC | Create an editable playlist. |
| youtube_delete_playlistC | Delete an editable playlist. This is destructive. |
| youtube_rename_playlistC | Rename an editable playlist. |
| youtube_set_playlist_descriptionC | Set an editable playlist description. |
| youtube_add_videosC | Add video IDs to an editable playlist. |
| youtube_remove_videosB | Remove video IDs from an editable playlist. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool targets a distinct operation: cookie management (set/status), account info, playlist listing/retrieval, and playlist mutations (create/delete/rename/description/video add/remove). There is no overlap that would cause an agent to select the wrong tool; even similar-sounding tools like rename_playlist and set_playlist_description are clearly differentiated by their descriptions.
Most tools follow a clear verb_noun pattern with a consistent 'youtube_' prefix (e.g., youtube_list_playlists, youtube_get_playlist, youtube_create_playlist). However, three tools deviate: youtube_cookie_set and youtube_cookie_status use a noun_verb/noun_noun structure, and youtube_account_info is noun_noun. These are minor deviations that remain readable and predictable.
With 11 tools, the set is well-scoped for managing YouTube playlists without an API. It covers authentication, account info, playlist CRUD, and video membership without excessive redundancy. Each tool earns its place and the count is comfortably within the 3–15 ideal range.
The surface covers the core playlist lifecycle: authentication, listing, reading, creating, deleting, renaming, setting descriptions, and adding/removing videos. Minor gaps exist, such as tools for reordering or moving videos within a playlist, but these are non-essential for most workflows and can be worked around.