Skip to main content
Glama
tuitamogamer-gpt

youtube-mcp-server

by tuitamogamer-gpt
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Upload Caption Track

youtube_upload_caption

Upload a caption track to a YouTube video from a local file. Specify video ID, language, name, and file path.

Instructions

Upload a new caption track to a YouTube video from a local file.

The file is streamed directly from disk via fs.createReadStream. The MIME type is inferred from the file extension (.vtt → text/vtt, .srt → application/x-subrip, .sbv → text/x-google-video-subtitle, .ttml → application/ttml+xml).

Args

  • videoId (string, required): The video ID to attach the caption track to.

  • language (string, required): BCP-47 language tag for the track (e.g. "en", "fr-CA").

  • name (string, required): A human-readable display name for the track (e.g. "English (CC)").

  • filePath (string, required): Absolute local path to the caption file (.vtt, .srt, .sbv, .ttml).

  • isDraft (boolean, default false): Whether to upload the track as a draft (not publicly visible).

Returns

{
  "id": "string",
  "videoId": "string",
  "language": "string",
  "name": "string",
  "trackKind": "string",
  "isDraft": boolean
}

Examples

  • Upload an English SRT: videoId="dQw4w9WgXcQ", language="en", name="English", filePath="/captions/en.srt"

  • Upload as draft: videoId="dQw4w9WgXcQ", language="es", name="Spanish", filePath="/captions/es.vtt", isDraft=true

Errors

  • 400: Invalid language tag or file format not supported.

  • 403: You can only add captions to videos on your own channel. Check scopes (youtube.force-ssl).

  • 404: Video not found.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
videoIdYesThe video ID to attach the new caption track to.
languageYesBCP-47 language tag for the track (e.g. "en", "fr-CA").
nameYesHuman-readable display name for the track (e.g. "English (CC)").
filePathYesAbsolute local path to the caption file (.vtt, .srt, .sbv, .ttml).
isDraftNoUpload the track as a draft (not publicly visible). Default false.

Tool Definition Quality

A4.5/5.0
Behavior5/5

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

The description adds behavioral details beyond annotations: file streamed via fs.createReadStream, MIME type inference from extension, and error conditions (400, 403, 404). No contradiction with annotations.

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 headings (Args, Returns, Examples, Errors). Front-loaded with purpose. Every sentence adds value, no redundancy.

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?

Given no output schema, the description includes a JSON return example, error conditions, and examples. Covers action, params, return format, and errors completely for a file-upload caption tool.

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

Parameters4/5

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

Schema coverage is 100% with good descriptions. The description adds extra value: MIME type mapping for filePath, example argument values, and streaming detail. This exceeds the baseline of 3.

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 'Upload a new caption track to a YouTube video from a local file.' It specifies the action (upload), resource (caption track), and source (local file), distinguishing it from siblings like youtube_list_captions, youtube_download_caption, and youtube_delete_caption.

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?

The description lists errors (e.g., 403 for permissions) that imply prerequisites (must own video, need youtube.force-ssl scope), but does not explicitly state when to use this tool vs alternatives or provide when-not-to-use 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/tuitamogamer-gpt/youtube-mcp-server'

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