Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_preflight_resume_upload

Destructive

Validates and previews a resumable YouTube upload continuation for an existing upload session before resuming. Confirms file path, title, privacy, and publish settings to prevent incorrect continuation.

Instructions

Validate and preview an explicit resumable-upload continuation.

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>",
      "uploadId": "<uploadId>"
    },
    "name": "youtube_preflight_resume_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.
uploadIdYesUpload session ID returned by the upload preflight or youtube_get_upload_status.
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. Changed7 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."
    • addedInput schema / properties / uploadId / description
      Added value: +"Upload session ID returned by the upload preflight or youtube_get_upload_status."
  2. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

The only annotation is destructiveHint=true, and the description adds nothing about what could be destroyed, whether the upload session is consumed by this call, or what a 'preview' returns. 'Validate and preview' sits in tension with a destructive hint without resolving it, since the description never says explicitly whether side effects occur.

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

Conciseness3/5

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

Nine words, single sentence, front-loaded with the verbs — nothing wasted, but nothing earned either. The brevity is under-specification rather than economy for a tool with seven parameters and a destructive annotation.

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?

Given seven parameters, three required, a destructive hint and no output schema, one sentence cannot carry the load. The agent is left not knowing what the preview returns, whether files are uploaded, or how this pairs with youtube_resume_upload and youtube_get_upload_status.

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 seven parameters (including the enum on privacyStatus and the publishAt/publish coupling) are already documented in the schema. The description adds no parameter-level meaning beyond that, which lands exactly on the 3 baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb pair ('validate and preview') and object ('resumable-upload continuation') are specific enough to convey the general idea, but the crucial distinction from the actual upload action is left implicit. It never states what is validated or that nothing is uploaded, so an agent cannot tell from the description alone whether this mutates remote state.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when this tool should be chosen over the obvious sibling youtube_resume_upload, and no stated prerequisites even though the required uploadId implies a prior session. The one natural routing question the agent faces in this family — preflight first, then the real call — goes unanswered.

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