YouTube Subtitle MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | The port number for HTTP mode server deployment | 3000 |
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 |
|---|---|
| fetch_youtube_subtitlesA | Fetch subtitles/transcripts from YouTube videos. Supports multiple output formats (SRT, VTT, TXT, JSON) and language selection. Returns complete subtitle content with timestamps. |
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, distinct purpose focused on fetching YouTube subtitles.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'fetch_youtube_subtitles' follows a clear verb_noun pattern, but no comparison is needed.
A single tool is too few for a server with the apparent scope of YouTube subtitle management, as it lacks operations like searching for videos, handling errors, or managing subtitle files. This minimal set may cause agent failures due to incomplete functionality.
The server is severely incomplete for its domain; it only provides fetching subtitles but lacks essential operations such as searching for videos, uploading or editing subtitles, or handling multiple videos. This creates significant gaps in coverage for subtitle-related workflows.