YouTube MCP Server
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_transcriptC | YouTubeの字幕をURLまたは動画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 single tool has a clear and distinct purpose focused on retrieving transcripts from YouTube.
A single tool inherently has perfect naming consistency as there are no other tools to compare it against. The tool name 'get_transcript' follows a clear verb_noun pattern.
One tool is too few for a server named 'YouTube MCP Server', which suggests a broader scope. A single transcript retrieval tool feels incomplete for typical YouTube operations like searching videos, listing playlists, or managing uploads.
The tool surface is severely incomplete for a YouTube server. It only covers transcript retrieval, with no tools for core YouTube functionalities such as video search, metadata retrieval, playlist management, or user interactions, leaving significant gaps.