Youtube138 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API 密钥 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| auto_completeD | Auto Complete |
| trendingD | Trending |
| homeD | Home |
| searchD | Search |
| channel_channelsD | Channel Channels |
| channel_searchD | Channel Search |
| channel_playlistsC | Channel Playlists |
| channel_detailsD | Channel Details |
| channel_communityD | Channel Community |
| channel_videosD | Channel Videos |
| channel_details_v2D | Channel Details (v2) |
| video_commentsD | Video Comments |
| video_related_contentsD | Video Related Contents |
| video_streaming_dataD | Video Streaming Data |
| video_detailsD | Video Details |
| video_details_v2D | Video Details (v2) |
| community_post_commentsD | Community Post Comments |
| community_post_detailsD | Community Post Details |
| playlist_videosD | Playlist Videos |
| playlist_detailsD | Playlist Details |
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 20 tools
Most tools have distinct purposes targeting different YouTube resources (channels, videos, playlists, community posts), but there is notable overlap with 'channel_details' and 'channel_details_v2' which appear to be redundant versions, and 'search' and 'channel_search' could cause confusion about scope. The descriptions are clear enough to differentiate most tools, but the duplication and similar naming for search functions introduce ambiguity.
The naming follows a consistent snake_case pattern with a clear resource_action structure (e.g., 'video_comments', 'playlist_details'), which is predictable and readable. However, there are minor deviations such as 'auto_complete' and 'home' that don't fit the pattern as neatly, and the use of 'v2' suffixes for some tools breaks consistency slightly.
With 20 tools, the count is on the higher side for a YouTube API server, bordering on heavy but still manageable given the domain's complexity. It covers various aspects like channels, videos, playlists, and community features, but it might feel slightly bloated with redundant tools like the 'v2' versions, suggesting it could be streamlined without losing functionality.
The tool set provides comprehensive coverage for browsing and retrieving YouTube data, including channels, videos, playlists, community posts, comments, and search functionalities. Minor gaps exist, such as lack of tools for creating or modifying content (e.g., uploading videos or posting comments), but for a read-focused server, it covers the core viewing and discovery workflows well without dead ends.