Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_preflight_upload

Destructive

Validate and preview a private resumable video upload before publishing to confirm file and metadata readiness and catch upload issues early.

Instructions

Validate and preview a private resumable video upload.

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>"
    },
    "name": "youtube_preflight_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesVideo title; leading and trailing whitespace is trimmed.
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.
descriptionNoVideo description, up to 5000 characters.
privacyStatusNoVisibility: private, unlisted or public.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.3.1
    • 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

C2.8/5.0
Behavior1/5

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

The description says the tool will 'Validate and preview' an upload, which strongly implies a non-mutating dry run, while the annotations declare destructiveHint=true. This is a direct behavioral contradiction, and the description does not clarify what side effects, if any, the preflight creates or cleans up.

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?

The description is a single front-loaded sentence with no filler. It is maximally concise, though its brevity contributes to gaps captured in other dimensions.

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 a six-parameter preflight tool with no output schema and a destructiveHint annotation, the description is too thin. It does not explain the relationship to youtube_upload_video, what validation results are returned, or what side effects the preview has.

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

Parameters2/5

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

Schema coverage is 100%, so the schema already documents all six parameters in detail. The description adds little parameter meaning and its use of 'private' is potentially misleading because the schema's privacyStatus enum also supports unlisted and public.

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 uses specific verbs ('Validate and preview') and identifies the resource ('private resumable video upload'), so the basic purpose is clear. However, it does not explicitly distinguish this preflight tool from the actual upload sibling youtube_upload_video or from youtube_preflight_resume_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?

The 'preflight' naming and 'validate and preview' phrasing imply this should be used before an actual upload, but there is no explicit statement of when to use it, when not to use it, or which sibling to call instead. Usage is inferable but not guided.

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