youtube-playlists-mcp
Related Servers
Alternatives to youtube-playlists-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to search videos, channels, and playlists, retrieve video metadata, transcripts, and comments via the YouTube Data API v3.59 PyPI72MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to search videos, read channels, browse playlists, fetch comments, and get transcripts from YouTube using the YouTube Data API v3 and InnerTube API for captions.2GPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search for music and create/manage playlists on YouTube Music via OAuth 2.0 authentication.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with YouTube through the YouTube Data API, allowing users to search for videos, playlists, and channels, generate video titles using AI, and manage YouTube content through natural language commands.22ISC
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with YouTube channels, providing analytics, video metadata updates, transcript extraction, and comment management through official Google APIs with OAuth 2.0.MIT
- AlicenseAqualityCmaintenanceEnables AI models to interact with YouTube content including video details, transcripts, channel information, playlists, and search functionality through the YouTube Data API.797 npm11MIT
TDQS
Scored across 6 tools
Each tool targets a distinct resource+action: listing playlists vs. listing a playlist's items vs. adding an item vs. removing an item vs. creating a playlist vs. searching videos. The descriptions explicitly warn about the playlistItemId vs. videoId distinction, eliminating the one plausible confusion point.
All six tools follow a consistent snake_case verb_noun pattern (list_, add_, remove_, create_, search_). The 'my' qualifier in list_my_playlists is a minor semantic variation but the structure remains predictable.
Six tools is well-scoped for a playlist management server — every tool covers a distinct operation with no redundancy. Quota-cost annotations further justify each tool's existence and usage.
The surface covers list/create/add/remove plus search, but there is no update_playlist (rename, change description/privacy) and no delete_playlist, so the playlist lifecycle is open-ended. Agents asked to rename or delete a playlist hit a dead end despite create being present.