HasData

youtube_video: GET /

hasdata_youtube_video_getYoutubeVideo

Read-only

Get YouTube Video Data

Fetches a single YouTube video by its 11-character videoId. Returns title, thumbnail, raw + normalized views and likes, lengthSeconds, publish date, category, keywords/tags, isFamilySafe / isUnlisted flags, the uploading channel (id, link, subscribers, avatar), the full description with parsed links and hashtags, available captions tracks (with kind: asr for auto-generated), Content-ID music matches (song/artist/album), creator socialLinks, and the relatedVideos, endScreenVideos, and relatedShorts rails. Use to enrich a video URL with metadata, monitor view/like growth, extract music or sponsor/affiliate links, gather features for recommender or RAG pipelines, or detect caption tracks before calling the YouTube Transcript endpoint.

Input Schema

TableJSON Schema

Name	Required	Description
`v`	Yes	11-character YouTube video ID — the value of the `v=` query parameter in a watch URL (e.g. `dQw4w9WgXcQ` for `https://www.youtube.com/watch?v=dQw4w9WgXcQ`).
`gl`	No	The two-letter country code for the country you want to limit the search to. Provide one exact documented value (245 allowed), e.g. `ac`, `af`.
`hl`	No	The two-letter language code for the language you want to use for the search. Provide one exact documented value (159 allowed), e.g. `af`, `ak`.
`deviceType`	No	Device type for the request.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedJul 24, 2026

changedInput schema / properties / gl / description

Previous value: -"The two-letter country code for the country you want to limit the search to."New value: +"The two-letter country code for the country you want to limit the search to. Provide one exact documented value (245 allowed), e.g. `ac`, `af`."

removedInput schema / properties / gl / enum

Removed value: -[
-  "ac",
-  "af",
-  "al",
-  "dz",
-  "as",
-  "ad",
-  "ao",
-  "ai",
-  "aq",
-  "ag",
-  "ar",
-  "am",
-  "aw",
-  "au",
-  "at",
-  "az",
-  "bs",
-  "bh",
-  "bd",
-  "bb",
-  "by",
-  "be",
-  "bz",
-  "bj",
-  "bm",
-  "bt",
-  "bo",
-  "ba",
-  "bw",
-  "bv",
-  "br",
-  "io",
-  "bn",
-  "bg",
-  "bf",
-  "bi",
-  "kh",
-  "cm",
-  "ca",
-  "cv",
-  "ky",
-  "cf",
-  "td",
-  "cl",
-  "cn",
-  "cx",
-  "cc",
-  "co",
-  "km",
-  "cg",
-  "cd",
-  "ck",
-  "cr",
-  "ci",
-  "hr",
-  "cu",
-  "cy",
-  "cz",
-  "dk",
-  "dj",
-  "dm",
-  "do",
-  "ec",
-  "eg",
-  "sv",
-  "gq",
-  "er",
-  "ee",
-  "et",
-  "fk",
-  "fo",
-  "fj",
-  "fi",
-  "fr",
-  "gf",
-  "pf",
-  "tf",
-  "ga",
-  "gm",
-  "ge",
-  "de",
-  "gg",
-  "gh",
-  "gi",
-  "gr",
-  "gl",
-  "gd",
-  "gp",
-  "gu",
-  "gt",
-  "gn",
-  "gw",
-  "gy",
-  "ht",
-  "hm",
-  "va",
-  "hn",
-  "hk",
-  "hu",
-  "im",
-  "is",
-  "in",
-  "id",
-  "ir",
-  "iq",
-  "ie",
-  "il",
-  "it",
-  "je",
-  "jm",
-  "jp",
-  "jo",
-  "kz",
-  "ke",
-  "ki",
-  "kp",
-  "kr",
-  "kw",
-  "kg",
-  "la",
-  "lv",
-  "lb",
-  "ls",
-  "lr",
-  "ly",
-  "li",
-  "lt",
-  "lu",
-  "me",
-  "mo",
-  "mk",
-  "mg",
-  "mw",
-  "my",
-  "mv",
-  "ml",
-  "mt",
-  "mh",
-  "mq",
-  "mr",
-  "mu",
-  "yt",
-  "mx",
-  "fm",
-  "md",
-  "mc",
-  "mn",
-  "ms",
-  "ma",
-  "mz",
-  "mm",
-  "na",
-  "nr",
-  "np",
-  "nl",
-  "an",
-  "nc",
-  "nz",
-  "ni",
-  "ne",
-  "ng",
-  "nu",
-  "nf",
-  "mp",
-  "no",
-  "om",
-  "pk",
-  "pw",
-  "ps",
-  "pa",
-  "pg",
-  "py",
-  "pe",
-  "ph",
-  "pn",
-  "pl",
-  "pt",
-  "pr",
-  "qa",
-  "re",
-  "ro",
-  "ru",
-  "rw",
-  "sh",
-  "kn",
-  "lc",
-  "pm",
-  "vc",
-  "ws",
-  "sm",
-  "st",
-  "sa",
-  "sn",
-  "rs",
-  "sc",
-  "sl",
-  "sg",
-  "sk",
-  "si",
-  "sb",
-  "so",
-  "za",
-  "gs",
-  "es",
-  "lk",
-  "sd",
-  "sr",
-  "sj",
-  "sz",
-  "se",
-  "ch",
-  "sy",
-  "tw",
-  "tj",
-  "tz",
-  "th",
-  "tl",
-  "tg",
-  "tk",
-  "to",
-  "tt",
-  "tn",
-  "tr",
-  "tm",
-  "tc",
-  "tv",
-  "ug",
-  "ua",
-  "ae",
-  "uk",
-  "gb",
-  "us",
-  "um",
-  "uy",
-  "uz",
-  "vu",
-  "ve",
-  "vn",
-  "vg",
-  "vi",
-  "wf",
-  "eh",
-  "ye",
-  "zm",
-  "zw"
-]

changedInput schema / properties / hl / description

Previous value: -"The two-letter language code for the language you want to use for the search."New value: +"The two-letter language code for the language you want to use for the search. Provide one exact documented value (159 allowed), e.g. `af`, `ak`."

removedInput schema / properties / hl / enum

Removed value: -[
-  "af",
-  "ak",
-  "sq",
-  "ws",
-  "am",
-  "ar",
-  "hy",
-  "az",
-  "eu",
-  "be",
-  "bem",
-  "bn",
-  "bh",
-  "xx-bork",
-  "bs",
-  "br",
-  "bg",
-  "bt",
-  "km",
-  "ca",
-  "chr",
-  "ny",
-  "zh-cn",
-  "zh-tw",
-  "zh-hk",
-  "co",
-  "hr",
-  "cs",
-  "da",
-  "nl",
-  "xx-elmer",
-  "en",
-  "eo",
-  "et",
-  "ee",
-  "fo",
-  "tl",
-  "fil",
-  "fi",
-  "fr",
-  "fy",
-  "gaa",
-  "gl",
-  "ka",
-  "de",
-  "el",
-  "kl",
-  "gn",
-  "gu",
-  "xx-hacker",
-  "ht",
-  "ha",
-  "haw",
-  "iw",
-  "he",
-  "hi",
-  "hu",
-  "is",
-  "ig",
-  "id",
-  "ia",
-  "ga",
-  "it",
-  "ja",
-  "jw",
-  "kn",
-  "kk",
-  "rw",
-  "rn",
-  "xx-klingon",
-  "kg",
-  "ko",
-  "kri",
-  "ku",
-  "ckb",
-  "ky",
-  "lo",
-  "la",
-  "lv",
-  "ln",
-  "lt",
-  "loz",
-  "lg",
-  "ach",
-  "mk",
-  "mg",
-  "my",
-  "ml",
-  "mt",
-  "mv",
-  "mi",
-  "mr",
-  "mfe",
-  "mo",
-  "mn",
-  "ms",
-  "sr-me",
-  "ne",
-  "pcm",
-  "nso",
-  "no",
-  "nn",
-  "oc",
-  "or",
-  "om",
-  "ps",
-  "fa",
-  "xx-pirate",
-  "pl",
-  "pt",
-  "pt-br",
-  "pt-pt",
-  "pa",
-  "qu",
-  "ro",
-  "rm",
-  "nyn",
-  "ru",
-  "gd",
-  "sr",
-  "sh",
-  "st",
-  "tn",
-  "crs",
-  "sn",
-  "sd",
-  "si",
-  "sk",
-  "sl",
-  "so",
-  "es",
-  "es-419",
-  "su",
-  "sw",
-  "sv",
-  "tg",
-  "ta",
-  "tt",
-  "te",
-  "th",
-  "ti",
-  "to",
-  "lua",
-  "tum",
-  "tr",
-  "tk",
-  "tw",
-  "ug",
-  "uk",
-  "ur",
-  "uz",
-  "vu",
-  "vi",
-  "cy",
-  "wo",
-  "xh",
-  "yi",
-  "yo",
-  "zu"
-]

AddedMay 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only, non-destructive, open-world reads, so the safety profile is covered. The description adds genuine behavioral context: the exact shape of the payload (raw + normalized counts, asr caption kinds, Content-ID music matches, rail videos), which an agent cannot get elsewhere since there is no output schema.

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-loads purpose in the first line, then spends the bulk on the return payload enumeration, which is justified because no output schema exists. It is dense but every clause carries information; no filler sentences.

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?

For a single-resource GET with no output schema, the description covers identity of the resource, returned fields, and usage contexts. Nothing an agent needs to call it correctly or interpret the result is missing.

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?

Schema description coverage is 100%, so all four parameters including the gl/hl codes and deviceType enum are already documented in the schema. The description's mention of the 11-character videoId only restates what the schema says, so the baseline 3 is appropriate.

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?

States a specific verb and resource (fetch a single YouTube video by ID) and immediately enumerates the returned resource's key attributes. It distinguishes itself from the youtube_transcript sibling and from channel/search siblings by scoping to one video.

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?

Lists concrete use cases (enrich a URL, monitor view/like growth, extract music or affiliate links, RAG features) and routes the agent to the YouTube Transcript endpoint for caption fetching. There is no explicit 'when not to use' or alternative for the search/channel siblings, so it stops short of a 5.

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

All HasData tools Inspect

Try in Browser

Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?