Skip to main content
Glama
tuitamogamer-gpt

youtube-mcp-server

by tuitamogamer-gpt
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Download Caption Track

youtube_download_caption
Read-onlyIdempotent

Download subtitle tracks from YouTube videos by caption ID. Supports SRT, VTT, or SBV formats and auto-translation to other languages.

Instructions

Download the raw content of a caption track by its ID.

If outPath is provided the content is written to that local file path and a confirmation message is returned. Otherwise the caption text is returned directly (truncated to the character limit if necessary).

Args

  • captionId (string, required): The caption track ID to download.

  • format ("srt" | "vtt" | "sbv", optional): Subtitle format. Defaults to the track's native format when omitted.

  • tlang (string, optional): ISO 639-1 language code for auto-translated output (e.g. "fr", "de").

  • outPath (string, optional): Absolute local path to write the caption file to.

Returns

  • Without outPath: the raw caption file content as a text string.

  • With outPath: a confirmation string "Written N bytes to <path>".

JSON shape (structured) when content returned inline:

{ "captionId": "string", "format": "string|null", "tlang": "string|null", "content": "string" }

Examples

  • Download as SRT: captionId="AYtvM...", format="srt"

  • Translate to French and save: captionId="AYtvM...", tlang="fr", outPath="/tmp/fr.vtt"

Errors

  • 403: Captions can only be downloaded for videos on your own channel. Check scopes (youtube.force-ssl).

  • 404: Caption track not found.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
captionIdYesThe caption track ID to download.
formatNoSubtitle format: "srt", "vtt", or "sbv". Omit to use the track's native format.
tlangNoISO 639-1 language code for auto-translated output (e.g. "fr").
outPathNoAbsolute local file path to write the caption content to. When provided, returns a confirmation instead of the content.

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

Discloses truncation behavior, write-to-file vs inline return, error codes (403, 404), and aligns perfectly with annotations (readOnly, idempotent).

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

Conciseness5/5

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

Well-structured with clear sections, front-loaded purpose, and efficient use of space.

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

Completeness5/5

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

Covers all aspects: input, output, error handling, examples. No gaps given the complexity and schema richness.

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?

Adds significant value beyond schema: default format behavior, return types, examples. Schema coverage is 100% but the description enriches each parameter.

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 the verb 'download' and resource 'caption track', distinguishing it from sibling tools like 'list', 'delete', and 'update'.

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?

Provides clear context on when to use (with caption ID) and constraints (own channel, scopes), though does not explicitly mention 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/tuitamogamer-gpt/youtube-mcp-server'

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