mcp-youtube-search
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SERP_API_KEY | Yes | Your SerpAPI API key. Get one at https://serpapi.com/ |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_youtubeA | Search YouTube for videos: title, link, channel, views, publish date, duration and description. |
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
With only a single tool, there is no possibility of overlap or misselection between tools. The one tool's purpose (YouTube video search) is unambiguous.
The lone tool uses a clean verb_noun snake_case pattern (search_youtube). There is no inconsistent convention to conflict with it.
A single tool is thin even for a search-focused server; it covers exactly one query type. It earns its place but leaves the surface feeling minimal.
Search alone leaves notable gaps: no tool to fetch a specific video's full details, channel info, comments, or transcripts. Core search is covered but agents will hit dead ends for follow-up queries.