Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_cancel_upload

Destructive

Cancels an approved resumable YouTube upload session using its upload ID and approval ID, stopping the upload after a confirmed cancel preview.

Instructions

Cancel an approved resumable upload 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": {
      "approvalId": "<approvalId>",
      "uploadId": "<uploadId>"
    },
    "name": "youtube_cancel_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to execute; set it only after youtube_approve approved this exact preview.
uploadIdYesUpload session ID returned by the upload preflight or youtube_get_upload_status.
approvalIdYesApproval ID from the youtube_preflight_cancel_upload preview, after approving it with youtube_approve.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.1
    • addedInput schema / properties / approvalId / description
      Added value: +"Approval ID from the youtube_preflight_cancel_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 / uploadId / description
      Added value: +"Upload session ID returned by the upload preflight or youtube_get_upload_status."
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

The destructiveHint=true annotation already signals a destructive operation, and "Cancel" is consistent with it. Beyond that the description adds nothing: it doesn't say partial upload data is discarded, whether cancellation is reversible, or that it only succeeds against a matching approved preview.

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?

A single front-loaded sentence with no filler, and the key qualifier ("approved") is placed before the resource. It is arguably over-compressed for a destructive tool, but nothing is wasted.

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 schema carries the full approval workflow and all three parameters, and destructiveHint flags the risk, so an agent can call it correctly. However, for a destructive tool with no output schema, the description itself leaves the post-call state and any failure modes unexplained.

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%, and every parameter (confirm, uploadId, approvalId) is documented with its source and the approval gating condition. The description adds no parameter meaning beyond that, 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?

Specific verb (cancel) plus a precise resource (an approved resumable upload session), so the agent knows exactly what is being terminated. It implicitly separates itself from youtube_preflight_cancel_upload by requiring an already-approved session, though it never names that sibling.

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?

The description gives no when-to-use guidance and never names the mandatory sequencing: youtube_preflight_cancel_upload → youtube_approve → this tool. A reader must infer the prerequisite from the schema's approvalId description rather than from the tool description.

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