Skip to main content
Glama

YouTube video metadata

get_youtube_video_metadata
Read-only

Fetch structured metadata for a YouTube video including title, description, views, likes, channel info, and technical details.

Scope: one query per call. To run many queries in one pass, or to write results to disk instead of into the conversation, use the ScrapingBee CLI — scrapingbee <command> --input-file queries.txt --output-dir results.

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_id": "<video_id>"
    },
    "name": "get_youtube_video_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
video_idYesThe unique YouTube video ID (e.g., 'rfscVS0vtbw').

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds real behavioral context on top — the result is delivered into the conversation rather than written to disk, and the tool is scoped to one query per call. It says nothing about failure modes for invalid or private video IDs, which is the main remaining gap.

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 two-part structure is front-loaded and efficient: what you get, then the scope/alternative constraint. The embedded CLI example with flags is slightly verbose but earns its place by being directly actionable, and no sentence is filler.

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 one-parameter read tool with an output schema and readOnlyHint, the description covers purpose, returned fields, and the batching escape hatch. The only missing piece an agent might want is what happens when the video is unavailable or the ID is malformed.

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?

With a single parameter at 100% schema coverage, the schema already explains video_id with a concrete example ('rfscVS0vtbw'), so the baseline applies. The description adds no syntax or format detail beyond that, but it does imply the identifier is a single video rather than a URL or channel.

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 opens with a specific verb and resource ("Fetch structured metadata for a YouTube video") and enumerates the returned fields (title, description, views, likes, channel info, technical details), so an agent knows exactly what it gets. It does not explicitly contrast itself with nearby siblings like get_youtube_video_subtitles or get_youtube_search_results, though the single-video-ID framing makes the distinction largely inferable.

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?

It gives a clear when-not rule: for many queries in one pass, or when results should go to disk rather than the conversation, use the ScrapingBee CLI, and it shows the exact invocation. What it omits is routing between this tool and its YouTube siblings (subtitles, search results), so the guidance covers batching but not tool selection.

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