Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_get_upload_status

Read-only

Monitor the progress of a resumable YouTube upload. Retrieve the current status of an upload session using only the session ID without transferring media bytes.

Instructions

Probe a resumable upload session without sending media bytes.

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_get_upload_status"
  }
}

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

B3.3/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds useful context that it probes without sending media bytes, but it does not explain what status information is returned, whether the session remains active, or how to interpret completion/resume state.

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 redundant or wasted wording. It communicates the operation and the no-media-transfer constraint efficiently.

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 tool is simple, with one fully described parameter and a readOnly annotation, but there is no output schema and the description does not explain what the probe returns. For a status-check tool, the response meaning is important, so the definition is adequate but incomplete.

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 coverage is 100%, and the single uploadId parameter is fully documented in the schema as the session ID returned by preflight or this status tool. The description itself adds no further parameter guidance, 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: probing a resumable upload session. It also clarifies that no media bytes are sent, which helps distinguish this status check from actual upload/resume operations. It does not explicitly name sibling tools such as youtube_resume_upload or youtube_cancel_upload, so it falls short of full sibling differentiation.

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 implies the tool is for checking an upload session's state, but it gives no explicit guidance on when to use it versus alternatives like youtube_resume_upload, youtube_cancel_upload, or youtube_upload_video. There are no exclusions or decision rules.

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