YouTube Search MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REDIS_DB | No | Redis database number | 0 |
| REDIS_HOST | No | Redis host for caching | localhost |
| REDIS_PORT | No | Redis port | 6379 |
| PYTHONUNBUFFERED | No | Ensure Python output is unbuffered | 1 |
| MCP_SEARCH_RETRIES | No | Retry attempts on search failure | 3 |
| MCP_SEARCH_TIMEOUT | No | Search operation timeout in seconds | 15 |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| youtube_searchA | 搜尋 YouTube 影片。支援按關鍵字搜尋，可指定結果數量限制（1-100，預設 1）和排序方式（relevance 或 date，預設 relevance）。返回包含視頻 ID、標題、頻道、URL、觀看次數和上傳日期的完整結果。 |
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 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The single tool has a clear purpose.
With only one tool, naming consistency is perfect. The name 'youtube_search' follows a clear verb_noun pattern.
The server has only one tool, which feels thin for a video platform. While it covers basic search, typical servers offer more endpoints for a richer interaction.
The server only provides search functionality. Missing features like fetching video details, channel information, or trending videos create significant gaps for a comprehensive YouTube tool.