Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_preflight_cancel_upload

Destructive

Preview cancellation of a resumable YouTube upload session to confirm the correct upload ID before stopping an unintended transfer.

Instructions

Preview cancellation of a 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": {
      "uploadId": "<uploadId>"
    },
    "name": "youtube_preflight_cancel_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
uploadIdYesUpload session ID returned by the upload preflight or youtube_get_upload_status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.1
    • 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
Behavior1/5

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

The description says 'Preview cancellation', which strongly implies a non-mutating check, while the annotations declare destructiveHint=true. That leaves the agent with contradictory signals about whether the upload session is actually cancelled or merely validated, and the description adds no clarification about reversibility, permissions, or side effects.

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 or redundancy. It is appropriately sized for a one-parameter tool, though its brevity contributes to the missing guidance elsewhere.

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 simple one-parameter preflight tool, the parameter context is adequately covered by the schema, but the description fails to resolve the critical behavioral ambiguity between 'preview' and destructiveHint=true. The agent still lacks enough information to know whether invoking this tool has side effects.

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?

There is only one parameter and schema description coverage is 100%, so the schema already explains uploadId thoroughly. The description does not add any format, source, or validity details beyond what the schema provides, so baseline 3 is appropriate.

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 ('Preview cancellation') and resource ('resumable upload session'), so the agent knows it is a preflight/dry-run operation rather than an actual cancel. It stops short of naming youtube_cancel_upload as the sibling that performs the real cancellation, so sibling differentiation is only 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?

The word 'Preview' implies this should be used before actually cancelling, but the description never explicitly says when to use it, when not to use it, or names the alternative youtube_cancel_upload. Usage is inferable but not stated.

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