YouTube Transcript Extractor 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 |
|---|---|
| youtube-transcript-extractorC | Extracts the transcript of a YouTube video. |
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's purpose is singular and clearly defined, so an agent cannot misselect among multiple options.
The single tool name follows a clear verb-noun pattern (youtube-transcript-extractor), and with no other tools to compare, consistency is inherently perfect. There are no deviations or mixed conventions to evaluate.
One tool is too few for a server that appears to handle YouTube transcript extraction, as it lacks complementary operations like listing videos, handling errors, or supporting multiple formats. This minimal scope may limit agent workflows and feels incomplete for the domain.
The server is severely incomplete for YouTube transcript extraction, as it only provides extraction without supporting operations like validation, search, or handling different transcript types. This creates significant gaps that could cause agent failures in real-world scenarios.