YouTube Tools MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAPIDAPI_KEY | Yes | Your RapidAPI key for transcript extraction | |
| DATABASE_PATH | No | Optional: Custom path for the video summaries database file | ./video_summaries.db |
| YOUTUBE_API_KEY | Yes | Your YouTube Data API v3 key for search functionality |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_youtube_transcriptB | Extract transcript from a YouTube video |
| search_youtubeB | Search for YouTube videos using the YouTube Data API v3 |
| fetchExistingVideoSummaryA | Fetch an existing video summary from the database |
| storeVideoSummaryB | Store or update a video summary in the database |
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 4 tools
Each tool has a clearly distinct purpose: searching YouTube, fetching transcripts, and retrieving/storing summaries. There is no overlap between tool responsibilities, so an agent can easily select the correct tool for a task.
The tool names mix conventions: 'get_youtube_transcript' and 'search_youtube' use snake_case and include 'youtube', while 'fetchExistingVideoSummary' and 'storeVideoSummary' use camelCase and omit the service name. The inconsistent verb choices (get vs fetch, store vs search) further reduce predictability.
With only 4 tools, the server is tightly scoped to its purpose of YouTube video search, transcript retrieval, and summary management. Each tool is necessary and there is no bloat, making the count appropriate for the domain.
The tool set covers the core workflows: search, transcript, and summary storage/retrieval. A delete summary tool is missing, but the store operation handles both create and update, so the surface is largely complete for the implied use case.