Skip to main content
Glama
YouTube MCP Server

YouTube MCP Server

Get video details

get_video_details
Read-onlyIdempotent

Retrieve full metadata for one or more YouTube videos, including views, likes, comments, duration, tags, and thumbnails. Invalid or unavailable IDs are listed separately.

Instructions

Full details for one or more videos: title, description, views, likes, comment count, duration, publish date, tags, thumbnails.

IDs that are deleted, private, or wrong are listed under not_found.

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_ids": "<video_ids>"
    },
    "name": "get_video_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
video_idsYesOne video ID, a comma-separated string of IDs, or a list of IDs (any number).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely new behavior not in annotations: that deleted, private, or invalid IDs are returned under a not_found bucket rather than erroring. The listed return fields add little since an output schema exists.

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?

Two sentences, front-loaded with the field inventory and followed by the failure-bucket note. The field enumeration partially overlaps the output schema, which is minor waste but nothing is confusing or padded.

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

Completeness4/5

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

For a single-parameter read tool with an output schema and full annotation coverage, the description covers purpose and partial-failure semantics adequately. It leaves only alternative-selection guidance unaddressed, which is a small gap given the many sibling retrieval tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 string, comma-separated, and list forms. The description reinforces the cardinality ('one or more videos'), adding a small amount of meaning beyond the schema without contradicting it.

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?

States a clear verb+resource ('Full details for one or more videos') and enumerates the exact fields returned, which cleanly separates it from analytics/insight siblings. It stops short of naming a sibling to disambiguate against, so it is clear but not maximally differentiated.

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 batch phrasing ('one or more') implies usage for looking up already-known video IDs, and the not_found note hints at partial-failure handling. However, there is no explicit statement of when to prefer this over get_video_analytics, get_top_videos, or search_videos, so the guidance is only implied.

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