Skip to main content
Glama
PPiai

youtube-mcp

by PPiai

get_video_details

Retrieve detailed metadata for YouTube videos by providing video IDs. Access title, description, statistics, and more.

Instructions

Get detailed information about specific videos

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
video_idsYesList of YouTube video IDs
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Get detailed information', without specifying what 'detailed' entails, whether it includes statistics, thumbnails, etc. There is no mention of rate limits, authentication needs, or potential 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no redundancy. It is front-loaded with the verb and resource. However, it could benefit from a brief note on output or usage without being verbose. The conciseness is good but not exceptional.

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?

Given the simplicity of the tool (one parameter, no output schema, no annotations), the description is incomplete. It does not explain what 'detailed information' includes, such as metadata fields, or whether it handles missing IDs. An agent needs more context to use the tool effectively.

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%, so the baseline is 3. The description adds no extra meaning beyond the schema's 'List of YouTube video IDs' for the 'video_ids' parameter. It does not clarify format, constraints, or behavior (e.g., max IDs).

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 clearly states 'Get detailed information about specific videos', providing a specific verb and resource. However, it does not differentiate from sibling tools like 'get_video_comments' or 'get_trending_videos', which could also provide video details. A score of 4 is appropriate as it is clear but lacks sibling distinction.

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?

No guidance is provided on when to use this tool versus alternatives such as 'search_videos' or 'get_trending_videos'. There are no conditions, prerequisites, or exclusions mentioned, leaving the agent without context for tool selection.

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/PPiai/youtube-mcp'

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