YouTube MCP

Overview Schema Source Related Servers Discussions Admin

youtube_resume_upload

Destructive

Resume an approved YouTube upload by probing its existing session, enabling interrupted uploads to continue only after the required approval.

Instructions

Resume an approved upload only after probing its existing session.

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

Input Schema

Name	Required	Description
`title`	Yes	Video title; leading and trailing whitespace is trimmed.
`confirm`	No	Must be true to execute; set it only after youtube_approve approved this exact preview.
`publish`	No	Must be true when privacyStatus is public, as a separate confirmation.
`filePath`	Yes	Absolute path to the local video file to upload.
`uploadId`	Yes	Upload session ID returned by the upload preflight or youtube_get_upload_status.
`publishAt`	No	Future ISO 8601 time to publish; only valid with privacyStatus private.
`approvalId`	Yes	Approval ID from the youtube_preflight_resume_upload preview, after approving it with youtube_approve.
`description`	No	Video description, up to 5000 characters.
`privacyStatus`	No	Visibility: private, unlisted or public.

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.3.1Oct 31, 2026

addedInput schema / properties / approvalId / description

Added value: +"Approval ID from the youtube_preflight_resume_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."

addedInput schema / properties / uploadId / description

Added value: +"Upload session ID returned by the upload preflight or youtube_get_upload_status."

First observedv0.1.0Oct 29, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations expose only destructiveHint=true, so the description needs to carry weight. It does add the useful gating context that this must be an already-approved upload with a probed session, but it says nothing about what resuming actually does (finalize, publish, overwrite progress) or what happens if the session is stale.

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?

A single tight sentence with the action front-loaded and the precondition attached. No filler and nothing redundant with the schema.

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

Completeness3/5

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

The 9-parameter schema is fully documented, so the description needn't restate parameters, but for a destructive gated mutation it omits the orchestration sequence and outcome of resuming. One sentence is thin given it is the execution step in a preflight/approve workflow.

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%, with per-parameter docs covering confirm, approvalId, uploadId, publishAt, and privacyStatus dependencies. The description adds nothing beyond the schema, so the baseline of 3 applies.

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 gives a specific verb and resource ('Resume an approved upload') plus a precondition, so it is clearly distinct from youtube_upload_video. It never names the sibling tools that perform the approval or the session probe, leaving that mapping implicit.

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?

'Only after probing its existing session' implies a prerequisite ordering, but the description never names youtube_get_upload_status, youtube_preflight_resume_upload, or youtube_approve. There is no explicit when-not guidance versus starting a fresh upload with youtube_upload_video.

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

Deploy Server