YouTube MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| get_youtube_transcript_toolA | Extract English transcript with timestamps from a YouTube video using its URL or video ID. |
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 one tool, there is no possibility of ambiguity or overlap between tools. The tool has a clear, singular purpose focused on transcript extraction from YouTube videos.
The single tool name follows a clear verb_noun pattern (get_youtube_transcript_tool), which would be consistent if there were more tools. There are no naming conflicts or inconsistencies to evaluate.
A single tool is too few for a YouTube MCP server, which suggests a broader domain like video management, search, or analytics. This minimal toolset severely limits functionality and feels incomplete for the implied scope.
The toolset is severely incomplete for a YouTube server. It lacks basic operations such as searching videos, retrieving metadata, managing playlists, or handling comments. The single transcript tool covers only a narrow aspect of YouTube's capabilities.