Skip to main content
Glama
gridivit

mcp-youtube-transcript

by gridivit

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_transcript_languagesA

List the subtitle tracks available for a YouTube video.

Call this when you do not know which languages a video has, or after get_transcript reported that the requested language is unavailable.

Args: url: YouTube video URL (watch, youtu.be, shorts or embed form), or the bare 11-character video id.

Returns: One line per track: " - (manual|auto-generated)".

get_transcriptA

Get the full transcript text of a YouTube video.

Returns the whole transcript as plain text without timestamps. Long videos produce long text: a two-hour video is roughly 20-30 thousand words.

If the requested language is unavailable, English is used as a fallback. If neither exists, this fails and lists the languages the video does have - pick one of them and call again.

Args: url: YouTube video URL (watch, youtu.be, shorts or embed form), or the bare 11-character video id. language: Language code of the wanted transcript, e.g. "en", "ru", "de".

Returns: The transcript as a single plain-text string.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.7/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have distinct purposes: one lists available subtitle tracks, the other retrieves a transcript in a specified language. There is no overlap in functionality, and the descriptions clarify when to use each.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern: 'list_transcript_languages' and 'get_transcript'. This creates a predictable and readable convention.

Tool Count4/5

Two tools is slightly below the typical 3-15 range, but it is well-scoped for a focused YouTube transcript server. The count feels appropriate rather than thin, covering the core use cases.

Completeness5/5

The tool surface covers the essential lifecycle: discovering available languages and fetching the transcript. The fallback to English and error messaging that suggests other languages complement the workflow, leaving no obvious gaps.

Maintenance

ActivitySlowing
ResponsivenessNo issues