Skip to main content
Glama

video_info

Retrieve YouTube video metadata such as title, channel, stats, upload date, tags, chapters, and description text to inform research or content analysis.

Instructions

Get YouTube video metadata: title, channel, stats, upload date, tags, chapters, description.

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": "video_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
description_charsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden and does not meet it. It never states whether private/unlisted/age-restricted videos work, whether an API key or quota applies, or what happens on a bad URL — all material for a network-backed fetch.

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?

A single front-loaded sentence with no filler; the resource is stated first and the payload second. Nothing is wasted or buried.

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

Completeness3/5

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

An output schema exists, so the description is not obliged to explain return values, and the field list is a reasonable pointer. However, for a zero-annotation tool with an undocumented second parameter, the missing operational context (auth, failure modes, description_chars) leaves it only marginally adequate.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for two parameters, so the description must compensate and does not. 'url' is at least implied by 'YouTube video', but 'description_chars' (default 1500) is never mentioned, leaving the agent unaware that returned description length is controllable.

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 pairs a specific verb ('Get') with a specific resource ('YouTube video metadata') and enumerates the returned fields (title, channel, stats, upload date, tags, chapters, description). That field list implicitly separates it from transcript/comment siblings, though no sibling is named explicitly.

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?

There is no guidance on when to use this versus find_in_video, video_comments, or transcribe_video, and no prerequisites or exclusions. The agent must infer the routing decision from the returned-field list alone.

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