Skip to main content
Glama

YouTube video details

youtube_video
Read-onlyIdempotent

Get a public YouTube video, Short or live stream: title, description, exact publish time, length, views, likes, exact comment count, tags and hashtags, category, chapters, links in the description, thumbnail, live status, members-only and age-restricted flags, and its channel with subscriber count and verified badge. For what is said in it, call youtube_transcript; for its comments, youtube_comments.

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": {
      "url": "<url>"
    },
    "name": "youtube_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesA YouTube video link (watch, youtu.be, Shorts, live or embed link) or its 11-character id (_T8cn2J13-4).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds value beyond that by naming the returned payload breadth and by flagging that the target is a 'public' video while still reporting members-only and age-restricted flags, which tells the agent how restricted content is surfaced. It does not discuss failure modes (deleted/private video) or rate limits, so it stops short of 5.

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?

Front-loaded with the action and scope, then the field inventory, then the sibling routing — a sensible order with no filler. The field enumeration is long but each item is concrete returned data, and the final routing sentence earns its place; the run-on field list is the only mild cost.

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?

There is no output schema, so the description must carry return-value expectations, and it does so thoroughly by listing the fields and the embedded channel summary. For a single-parameter read tool that is largely sufficient; only error/edge-case behavior for unavailable videos is left implicit.

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?

Only one parameter and schema description coverage is 100%, and the schema already spells out accepted URL forms (watch, youtu.be, Shorts, live, embed) and the 11-character id form. The description adds nothing beyond that about the url argument, so this sits at the baseline where structured data does the work.

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?

Opens with a specific verb and resource ('Get a public YouTube video, Short or live stream') and then enumerates exactly what comes back: title, publish time, views, likes, comment count, tags, chapters, thumbnail, live status, and the owning channel with subscriber count and verified badge. An agent can distinguish it from youtube_transcript and youtube_comments without reading any schema.

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?

Explicitly routes the agent to alternatives with the condition that selects them: 'For what is said in it, call youtube_transcript; for its comments, youtube_comments.' This is a direct when-to-use-this-vs-sibling statement, not an inference.

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.

Resources