youtube-transcript
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEBSHARE_PASSWORD | No | Webshare proxy password. Optional; used together with WEBSHARE_USERNAME to route requests through a proxy. Leave empty to connect directly. | |
| WEBSHARE_USERNAME | No | Webshare proxy username. Optional; used to route YouTube requests through a proxy if YouTube blocks your requests. Leave empty to connect directly. |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_transcriptB | Get the caption transcript of a YouTube video, one [m:ss]-stamped line per caption. |
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
There is only one tool, so there is no possibility of ambiguity or misselection between tools. Its purpose (fetching a YouTube caption transcript) is unambiguous.
The single tool uses a clear, conventional snake_case verb_noun pattern (get_transcript). With only one name there is no inconsistency to speak of, and the name matches the server's stated purpose.
One tool is thin, but the server is deliberately scoped to a single capability and that tool earns its place. It falls just short of a full 5 because the surface offers no room for even closely related operations.
Core retrieval of a transcript is covered, but obvious adjacent operations are absent: listing available caption languages, selecting a language, or returning video metadata. Multi-language caption handling in particular is a notable gap that could cause agent failures.