Skip to main content
Glama

youtube_get_video_info

Retrieve rich metadata for a single YouTube video from its URL, including duration in seconds, to inspect and analyze video details.

Instructions

Rich metadata for one video — port of tube-bridge youtube_get_video_info.

Layer 1/2 (1 unit) → Layer 3 (yt-dlp, 0 units). ``duration`` in seconds.

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_get_video_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does add real behavioral context: a layered retrieval path (Layer 1/2 then yt-dlp fallback), the unit cost of each path, and that duration is returned in seconds. It omits what happens on failure, whether the yt-dlp fallback is slower or rate-limited, and any auth/quota implications beyond the raw unit counts.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose sentence is front-loaded and efficient, but the second sentence is opaque internal jargon ("Layer 1/2 (1 unit) → Layer 3 (yt-dlp, 0 units)") whose meaning depends on undocumented context. The "port of tube-bridge" note adds little for an agent deciding how to call the tool.

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 return values needn't be described, and the tool is simple with one parameter. However, with zero annotations and zero parameter description coverage, the definition should say more about input format and fallback behavior than it does.

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 the single required parameter `url`, so the description must compensate and does not. It never states whether `url` accepts a full watch URL, a short youtu.be link, or a bare video ID, leaving the only input underspecified.

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 specific resource and scope: "Rich metadata for one video," which tells an agent this is a single-video lookup rather than a search or channel listing. It does not explicitly name a sibling to distinguish itself from (e.g. youtube_get_transcript or youtube_get_channel_videos), but the resource boundary is clear.

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 when-to-use or when-not-to-use guidance. The description never says whether to prefer this over youtube_get_transcript, search_videos, or a channel-level call, and gives no prerequisite about which URL forms are accepted.

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