Skip to main content
Glama

Get video details

get_video_details
Read-only

Get the facts about one video without its transcript: title, channel, views, length, publish date, which caption languages exist (human-made or auto-generated), the full description, and the chapter list with a link to each chapter. Use it to decide whether a video is worth reading, to find the right lang code, or to read one chapter at a time with get_transcript_section.

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

Input Schema

NameRequiredDescriptionDefault
videoYesYouTube video URL or 11-character video ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context by listing exactly what data is returned and emphasizing that the transcript is not included, though it does not discuss auth or rate limits.

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?

Two tight sentences: the first front-loads what is returned, and the second lists the practical use cases. There is no redundant wording or unnecessary setup.

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 no output schema, the description carries the burden of explaining return values and does so thoroughly: title, channel, views, length, publish date, caption languages, full description, and chapter links. That is complete for a single-parameter read-only tool.

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?

There is only one parameter and schema coverage is 100%, so the schema already documents that it accepts a YouTube URL or 11-character video ID. The description adds 'one video' but no further syntax or format detail beyond the schema.

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?

States a specific verb and resource ('Get the facts about one video') and explicitly excludes the transcript, then enumerates the returned fields. It clearly distinguishes itself from transcript-oriented siblings such as get_transcript_section.

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

Usage Guidelines5/5

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

Gives three concrete use cases: deciding whether a video is worth reading, finding the right lang code, and reading one chapter at a time with get_transcript_section. The transcript exclusion also implicitly clarifies when not to use this tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.