Skip to main content
Glama
YouTube Personal Playlist noAPI MCP

YouTube Personal Playlist noAPI MCP

by bigbatmanorg

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
YOUTUBE_COOKIE_FILENoPath 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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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_playlistsB

List account-visible playlists as compact normalized data.

youtube_get_playlistA

Get one page of a playlist (Watch Later "WL" and Liked "LL" included). Each video has duration, channel, playable, view/age info, percent_watched and a link. page is 1-based and counts pages of limit videos; request next_page while has_more is true.

youtube_playlist_statsB

Summarize a whole playlist (Watch Later "WL" included): video count, total and remaining duration (also at 1.25x/1.5x/2x), watched and partially watched counts, unavailable and duplicate counts, and top channels.

youtube_clean_playlist_previewA

Preview a playlist clean-up without changing anything: lists exactly which videos would be removed and why, plus a plan_token for youtube_clean_playlist_apply. Show the list to the user before applying.

youtube_clean_playlist_applyA

Remove exactly the videos from a matching youtube_clean_playlist_preview. Requires the same arguments and its plan_token; fails with PLAN_CHANGED and removes nothing if the playlist changed since the preview. Special playlists such as Watch Later cannot be modified.

youtube_create_playlistB

Create an editable playlist, optionally with initial videos.

youtube_delete_playlistA

Delete an editable playlist. This is destructive and cannot be undone.

youtube_rename_playlistC

Rename an editable playlist.

youtube_set_playlist_descriptionC

Set an editable playlist description.

youtube_add_videosB

Add videos to an editable playlist.

youtube_remove_videosA

Remove videos from an editable playlist. Fails without changes if any requested video is not in the playlist.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 14 tools

Disambiguation4/5

Most tools target clearly distinct resources and actions (list/get/stats/create/delete/rename/add/remove). The only real overlap zone is youtube_remove_videos versus youtube_clean_playlist_preview/apply, but the descriptions clarify that one removes explicit IDs while the other is a token-guarded plan, and cookie_set vs cookie_status vs account_info are differentiated by their stated purpose.

Naming Consistency4/5

All names share a consistent 'youtube_' prefix and snake_case, which makes the set predictable. Minor deviation: the playlist tools use verb-first (youtube_list_playlists, youtube_create_playlist) while cookie and clean-up tools use noun-first (youtube_cookie_set, youtube_clean_playlist_apply), so the pattern is slightly mixed but still highly readable.

Tool Count5/5

Fourteen tools is well within a sensible range for a playlist-management server, and each tool earns its place: playlist lifecycle, read/inspect operations, a two-step clean-up flow, and cookie/auth handling. Nothing feels redundant or padding-like.

Completeness4/5

The surface covers full editable-playlist CRUD (create, delete, rename, describe, add, remove), read/inspection (list, get, stats), and a safe preview/apply clean-up flow, plus auth via cookies. Minor gaps remain: no reordering/moving of items within a playlist, no targeted search within a playlist, and no batch copy/transfer operation, though agents can work around these.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues