Skip to main content
Glama
l4b4r4b4b4

YouTube MCP Server

by l4b4r4b4b4
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

list_available_transcripts

Discover all available transcript languages for any YouTube video, including manual and auto-generated transcripts. Check languages before retrieving a transcript.

Instructions

List all available transcript languages for a YouTube video.

Discovers which transcript languages are available for a video,
including both manual and auto-generated transcripts.
Cached permanently as available transcripts don't change.

Args:
    video_id: YouTube video ID (from URL or search, e.g., "dQw4w9WgXcQ")

Returns:
    AvailableTranscripts dictionary with:
    - video_id: The video ID
    - available_languages: List of language codes (e.g., ["en", "es", "fr"])
    - transcript_info: Detailed info for each (language, is_generated, etc.)

Example:
    >>> transcripts = list_available_transcripts("nLwbNhSxLd4")
    >>> print(transcripts["available_languages"])
    ["en", "de", "es"]

Note:
    - Uses no YouTube API quota (third-party transcript API)
    - Cached permanently in youtube.content namespace
    - Call this first before requesting specific transcript

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
video_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

With no annotations, the description covers key behaviors: permanent caching, no YouTube API quota, and the return type structure. It does not mention potential errors (e.g., invalid video ID) but overall provides good behavioral context.

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 well-structured with sections, example, and notes. However, the caching boilerplate (ref_id, pagination) appears generic and may not apply to this small-result tool, adding slight verbosity. Otherwise concise and front-loaded.

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 low complexity (1 param) and presence of output schema, the description covers purpose, usage order, caching, and quota. It could mention error handling but is largely sufficient for an agent to use correctly.

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?

The single parameter 'video_id' is fully explained with an example value ('dQw4w9WgXcQ') and context (from URL or search), adding meaning beyond the schema's bare type definition. Schema coverage is 0% but description compensates fully.

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 it lists available transcript languages for a YouTube video, with specific verbs ('list', 'discovers') and resource ('transcript languages'). It distinguishes itself from siblings like 'get_full_transcript' by focusing on discovery and availability.

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 advises calling this tool first before requesting a specific transcript, and explains caching and quota benefits. However, it does not explicitly state when not to use it or mention alternatives, leaving some implicit guidance.

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