Skip to main content
Glama
fetchtranscript-mcp

fetchtranscript-mcp

Official

list_languages

Returns available transcript languages for a YouTube video ID, so you can pick a valid caption language before fetching the transcript.

Instructions

List available transcript languages for a YouTube video.

Args: video_id: YouTube video ID (11 characters)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "video_id": "<video_id>"
    },
    "name": "list_languages"
  }
}

Input Schema

NameRequiredDescriptionDefault
video_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it says nothing about whether auto-generated captions are included, how languages are ordered or labeled, whether a video with no captions returns an empty list or an error, or whether credentials are required. For a tool with zero annotation coverage this is a substantial gap.

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 purpose is front-loaded in a single clear sentence and the Args block is short and free of filler. The docstring-style formatting is slightly redundant with the schema but not wasteful.

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

Completeness3/5

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

This is a simple one-parameter read tool and an output schema exists, so return-value documentation is not needed. Still missing are edge-case behavior for videos without captions and the relationship to the transcript-fetching sibling, which matter for correct invocation.

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

Parameters3/5

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

Schema description coverage is 0% and the schema only labels the field 'Video Id', so the description does add real value by specifying the 11-character format. It still leaves open whether full URLs or other identifier forms are accepted, so it only partially compensates for the coverage gap.

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

Purpose4/5

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

States a specific verb and resource ('List available transcript languages for a YouTube video'), which is clearly distinguishable from siblings like get_transcript or get_video_metadata. It never explicitly contrasts itself with those siblings, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is a discovery step before requesting a transcript in a specific language. There is no explicit when-to-use statement, no mention of the natural follow-up tool, and no stated preconditions or exclusions.

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