Skip to main content
Glama
l4b4r4b4b4

YouTube MCP Server

by l4b4r4b4b4

get_full_transcript

Get the full transcript of a YouTube video including timestamps and plain text. Automatically handles large transcripts with caching.

Instructions

Get the complete transcript for a YouTube video.

Retrieves the full transcript with all entries and timestamps.
For large transcripts (>2KB), RefCache automatically returns a preview
with a reference that can be paginated using get_cached_result.
Cached permanently as transcript content doesn't change.

Args:
    video_id: YouTube video ID (e.g., "dQw4w9WgXcQ")
    language: Language code (e.g., "en"). If empty, uses first available

Returns:
    FullTranscript dictionary with:
    - video_id, language
    - transcript: List of entries with text, start time, duration
    - full_text: Complete transcript as plain text

Example:
    >>> full = get_full_transcript("nLwbNhSxLd4", language="en")
    >>> print(len(full["transcript"]))
    150
    >>> print(full["full_text"][:100])

Note:
    - Uses no YouTube API quota
    - Cached permanently in youtube.content namespace
    - RefCache may return preview + reference for large transcripts
    - Use get_transcript_chunk for entry-by-entry pagination

Caching Behavior:

  • Parameters that accept reference strings can accept a ref_id from a previous tool call

  • Large results return ref_id + preview; use get_cached_result to paginate

  • All responses include ref_id for future reference

Ref input compatibility: Support depends on the tool's input schema/validation. Some strictly typed parameters may reject string ref_ids before resolution.

Full retrieval: Use get_cached_result(ref_id, full=True) to get the complete value.

Preview Size: server default. Override per-call with get_cached_result(ref_id, max_size=...).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
languageNo
video_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It discloses key behaviors: no YouTube API quota usage, permanent caching in youtube.content namespace, RefCache preview for large transcripts, and the return format. It does not contradict any annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is reasonably concise and well-structured, starting with a clear purpose, then args, returns, example, and notes. The generic caching behavior at the end slightly reduces conciseness but is still valuable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema, the description properly explains return values and caching behavior. It covers all major aspects: purpose, parameters, returns, caching, and alternatives, making it complete for a tool of moderate complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description thoroughly explains both parameters: video_id with an example, and language with default behavior. This adds significant value beyond the parameter names alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Get the complete transcript for a YouTube video' with a specific verb and resource. It distinguishes from siblings like get_transcript_chunk and get_cached_result, which handle pagination or partial retrieval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use the tool (retrieve full transcript) and mentions an alternative (get_transcript_chunk for entry-by-entry pagination). It also covers caching behavior and RefCache preview, but does not explicitly list when not to use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/l4b4r4b4b4/yt-api-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server