Skip to main content
Glama
tuitamogamer-gpt

youtube-mcp-server

Get Video Details

youtube_get_video
Read-onlyIdempotent

Fetch complete metadata for a YouTube video using its ID, including statistics, content details, and status.

Instructions

Fetch full metadata for a single video by ID.

Calls videos.list with parts: snippet, statistics, status, contentDetails, topicDetails, player, and liveStreamingDetails.

Args

  • videoId (string, required): the YouTube video ID (e.g. "dQw4w9WgXcQ")

  • response_format: "markdown" (default) or "json"

Returns JSON shape:

{
  "id": "dQw4w9WgXcQ",
  "title": "Never Gonna Give You Up",
  "description": "...",
  "publishedAt": "2009-10-25T06:57:33Z",
  "channelTitle": "Rick Astley",
  "categoryId": "10",
  "tags": ["rick astley", "pop"],
  "duration": "PT3M32S",
  "viewCount": "1400000000",
  "likeCount": "15000000",
  "commentCount": "2000000",
  "privacyStatus": "public",
  "embeddable": true,
  "madeForKids": false,
  "thumbnails": { ... },
  "statistics": { ... },
  "contentDetails": { ... }
}

Examples

  • Get video: { "videoId": "dQw4w9WgXcQ" }

  • JSON output: { "videoId": "dQw4w9WgXcQ", "response_format": "json" }

Errors

  • 404: video does not exist or is private/deleted

  • 403: insufficient permissions to view this video

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
videoIdYesYouTube video ID (e.g. dQw4w9WgXcQ).
response_formatNoOutput format: "markdown" (default) or "json".markdown
Behavior5/5

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

Annotations already indicate readOnly, destructive, idempotent, and openWorld hints. The description adds significant value by detailing the underlying API call (videos.list with specific parts), the return JSON shape, and error handling, providing complete behavioral transparency.

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 well-structured with sections (Args, Returns, Examples, Errors). It is front-loaded with the purpose, and every sentence adds value without redundancy. Appropriate length for the tool's complexity.

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?

The description covers all essential aspects: purpose, parameters, return format (including full JSON shape), examples, and error handling. Since there is no output schema, the return description is crucial and well-provided.

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?

Input schema has 100% coverage, so baseline is 3. The description adds example values and clarifies the response_format, but this is only marginal beyond the schema's descriptions. The schema already provides necessary semantics.

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 clearly states 'Fetch full metadata for a single video by ID,' using a specific verb and resource. It distinguishes from sibling tools like youtube_search (which lists multiple videos) and youtube_get_channel (which fetches channel details) by focusing on a single video's comprehensive metadata.

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?

The description provides error conditions (404, 403) that help determine when the tool can be used. However, it does not explicitly state when not to use it or suggest alternative tools for scenarios like fetching multiple videos or searching.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tuitamogamer-gpt/youtube-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server