Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_upload_video

Destructive

Starts an approved resumable video upload to YouTube from a local file, with visibility and publish controls. Requires an approval ID from the preview step.

Instructions

Start an approved resumable video upload. Public visibility also needs publish: true.

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": {
      "filePath": "<filePath>",
      "title": "<title>",
      "approvalId": "<approvalId>"
    },
    "name": "youtube_upload_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesVideo title; leading and trailing whitespace is trimmed.
confirmNoMust be true to execute; set it only after youtube_approve approved this exact preview.
publishNoMust be true when privacyStatus is public, as a separate confirmation.
filePathYesAbsolute path to the local video file to upload.
publishAtNoFuture ISO 8601 time to publish; only valid with privacyStatus private.
approvalIdYesApproval ID from the youtube_preflight_upload preview, after approving it with youtube_approve.
descriptionNoVideo description, up to 5000 characters.
privacyStatusNoVisibility: private, unlisted or public.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.3.1
    • addedInput schema / properties / approvalId / description
      Added value: +"Approval ID from the youtube_preflight_upload preview, after approving it with youtube_approve."
    • addedInput schema / properties / confirm / description
      Added value: +"Must be true to execute; set it only after youtube_approve approved this exact preview."
    • addedInput schema / properties / description / description
      Added value: +"Video description, up to 5000 characters."
    • addedInput schema / properties / filePath / description
      Added value: +"Absolute path to the local video file to upload."
    • addedInput schema / properties / privacyStatus / description
      Added value: +"Visibility: private, unlisted or public."
    • addedInput schema / properties / publish / description
      Added value: +"Must be true when privacyStatus is public, as a separate confirmation."
    • addedInput schema / properties / publishAt / description
      Added value: +"Future ISO 8601 time to publish; only valid with privacyStatus private."
    • addedInput schema / properties / title / description
      Added value: +"Video title; leading and trailing whitespace is trimmed."
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

The description adds some behavioral context beyond the destructiveHint annotation: the upload must be approved and public visibility needs a separate publish confirmation. It does not explain upload side effects, resumability behavior, authorization requirements, or what happens after starting the upload.

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?

Two sentences with zero filler, and the main action is front-loaded. The public-visibility confirmation is stated immediately after the core purpose.

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

Completeness2/5

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

For an eight-parameter upload tool with no output schema and a destructiveHint annotation, the description is too thin. It omits the preflight/approve workflow, relationship to resume_upload, upload status handling, and meaningful behavioral details beyond the publish gate.

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 100%, so all eight parameters are already documented in the schema. The description highlights publish: true but adds no additional meaning beyond the schema's own parameter descriptions.

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?

The description states a specific verb and resource: 'Start ... resumable video upload.' The word 'Start' distinguishes it from resume_upload, and 'approved' signals a prerequisite, though it does not fully differentiate from preflight_upload.

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?

It implies usage only after approval ('Start an approved...') and notes that public visibility requires publish: true. However, it does not explicitly name the prerequisite tools (youtube_preflight_upload and youtube_approve) or say when to choose this over resume_upload.

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

Deploy Server

Other Tools