Skip to main content
Glama

youtube_video

Fetch detailed metadata for any YouTube video: title, views, likes, description, keywords, channel info, key moments, and chapters. Use the video ID from the video URL.

Instructions

Scrapes detailed metadata for any YouTube video including title, views, likes, description, keywords, channel info, key moments, and chapters. [Credits: 5 API credits per successful request] Notes: Shares the single /youtube endpoint with all other YouTube tools; uses video_id (not v) to select Video-metadata behavior — this differs from Transcripts/Comments, which use v. ENDPOINT VERIFIED LIVE 2026-07-10: docs show bare /youtube but the working endpoint is /youtube/video. Param name is v (verified live; video_id returns an error). Returns: { video: {id, title, views, likes, author, published_time, description, keywords[], thumbnail}, channel: {id, name, link, subscribers, featured_channel:{id,name,link}, thumbnail}, comment: {total}, key_moments[], chapters[] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vYesYouTube video ID (docs call it video_id, but the live API requires the parameter name v). The YouTube Video ID, found in the video URL after `?v=` (e.g., for `youtube.com/watch?v=0e3GPea1Tyg`, the ID is `0e3GPea1Tyg`). This is the parameter that selects Video-metadata behavior on the shared /youtube endpoint (note the differing param name `video_id` vs `v` used by Transcripts/Comments).
countryNoTwo-letter country code for the YouTube video request (e.g., `us`, `uk`, `fr`). (default: us)
languageNoLanguage of the results. Possible values: `en`, `es`, `fr`, `de`, etc. (default: en)
Behavior5/5

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

With no annotations, the description fully discloses behavior: credits cost, live-verified endpoint (/youtube/video), parameter name must be v (not video_id), full return structure, and default values. No contradictions.

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 description is verbose, containing a full return JSON in text, verification notes, and credits info. While front-loaded with purpose, the length and unstructured details hurt conciseness.

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?

Given no output schema, the description compensates thoroughly: includes endpoint verification, parameter differences, default values, and a complete return object shape. All 3 parameters are explained. Very complete for a scraping tool.

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?

Schema coverage is 100%, baselining at 3. The description adds significant value: clarifies that v is the video ID from URL, warns against using video_id, and explains country/language defaults. The live verification note is extra context.

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?

The description clearly states it scrapes detailed metadata for any YouTube video, listing specific fields (title, views, likes, description, etc.). It distinguishes from sibling tools by noting the differing parameter name for video metadata vs. transcripts/comments.

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?

While it doesn't give explicit when-to-use/when-not-to-use statements, it contrasts with transcript and comment tools by pointing out the parameter difference. This implies its usage for video metadata, but lacks clear alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alessandrobenigni/ScrapingDog-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server