Skip to main content
Glama
Sign In
mcp-youtube

mcp-youtube

by mgcrea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

YouTube: Get Video

youtube_get_video
Read-only

Fetch full details for one YouTube video by ID, including status, stats, and processing progress for your own uploads. Use it to track when post-upload processing succeeds.

Instructions

One video in full: snippet, status (privacy, uploadStatus, failure/rejection reason, publishAt, madeForKids), contentDetails, statistics, and — for your own videos — processingDetails (processing progress after an upload) and fileDetails. Use it to follow processing after youtube_upload_video finishes: processingStatus goes processing → succeeded. Costs 1 quota unit.

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": {
      "video_id": "<video_id>"
    },
    "name": "youtube_get_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
video_idYesVideo id: the 11 characters after `v=` in a watch URL, e.g. "dQw4w9WgXcQ". youtube_list_videos lists this channel's.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description still adds meaningful behavior: the cost of 1 quota unit, the fact that processingDetails and fileDetails are only present for your own videos, and the processing-status lifecycle — all information not derivable from annotations. It stops short of describing failure modes such as a not-found or invalid video id.

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?

The returned parts are front-loaded in the first clause, then the primary use case, then the quota cost — a sensible ordering. The long parenthetical enumerating status sub-fields is dense but each item carries selection value; only minor trimming is possible.

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

Completeness5/5

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

With one required parameter and no output schema, the description's thorough enumeration of returned parts plus the conditional-availability note for processingDetails/fileDetails fully compensates. Nothing an agent needs in order to call this correctly is missing.

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 the single parameter already documents the 11-character id format with an example and a pointer to youtube_list_videos. The description adds no further meaning about video_id, so the baseline 3 applies.

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

Purpose5/5

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

The description names a single, specific resource ("One video in full") and enumerates exactly which parts are returned (snippet, status, contentDetails, statistics, processingDetails, fileDetails), so it is clearly distinguishable from the list/sibling tools. An agent knows precisely what this call yields without opening the schema.

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

Usage Guidelines4/5

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

It gives a concrete usage scenario: polling after youtube_upload_video to watch processingStatus go from `processing` to `succeeded`. That is real when-to-use guidance, though it offers no explicit exclusion or pointer to a sibling for the contrasting case (e.g. listing or searching many videos).

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