Skip to main content
Glama
tuitamogamer-gpt

youtube-mcp-server

Upload Video

youtube_upload_video

Upload local video files to YouTube. Handles large files, sets title, description, tags, privacy, and kid-friendly settings.

Instructions

Upload a local video file to YouTube.

Calls videos.insert with a resumable media upload. The file is streamed from disk via fs.createReadStream so large files are handled without loading them fully into memory.

Note: This operation costs approximately 1600 quota units.

Args

  • filePath (string, required): absolute path to the local video file

  • title (string, required): video title (shown on YouTube)

  • description (string, optional): video description

  • tags (string[], optional): tags / keywords

  • categoryId (string, optional): numeric category ID, default "22" (People & Blogs)

  • privacyStatus ("public"|"unlisted"|"private", optional, default "private")

  • madeForKids (boolean, optional, default false)

Returns Short confirmation markdown + the new video resource as structuredContent (includes the new video ID at structured.video.id).

Examples

  • Upload privately: { "filePath": "/tmp/myvideo.mp4", "title": "Test" }

  • Upload publicly: { "filePath": "/tmp/myvideo.mp4", "title": "Launch", "privacyStatus": "public" }

Errors

  • 400: file not found or unreadable, or required title missing

  • 403: upload scope missing — re-run npm run auth

  • 429: quota exceeded (upload costs ~1600 units)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filePathYesAbsolute path to the local video file to upload.
titleYesVideo title (required by YouTube).
descriptionNoVideo description.
tagsNoTags / keywords for the video.
categoryIdNoNumeric category ID (default "22" = People & Blogs).22
privacyStatusNoPrivacy status (default "private").private
madeForKidsNoDeclare video as made for kids (default false).
Behavior5/5

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

Annotations indicate it is not read-only (modifies state) and not idempotent; the description openly states it calls videos.insert with resumable upload, streams from disk, and costs quota. No contradictions.

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 (Args, Returns, Examples, Errors) and front-loaded with purpose. While slightly verbose, every sentence contributes useful information for an agent.

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 7 parameters and no output schema, the description fully explains return format (structured content with video ID) and error scenarios. Examples cover both minimal and full usage, ensuring an agent can invoke the tool 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?

Schema coverage is 100%, yet the description adds value by explaining filePath as absolute path, title as shown on YouTube, categoryId default mapping, and provides examples that illustrate parameter usage beyond schema constraints.

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 starts with 'Upload a local video file to YouTube,' which is a clear verb and resource. The title 'Upload Video' and sibling tools (e.g., youtube_update_video) further distinguish its purpose.

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 includes cost (1600 quota units), prerequisites (auth scope), and error conditions. While it does not explicitly contrast with alternatives, the context and sibling names make the usage case clear.

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