Skip to main content
Glama

HasData

by com.hasdata.mcp
OverviewDiscussionsAdmin

google_serp_short_videos: GET /

hasdata_google_serp_short_videos_getShortVideosSearchResults
Read-only

Get Short Videos Search Results

Scrapes the Google Short Videos carousel (TikTok, YouTube Shorts, Instagram Reels, etc.) for a query with location/uule, country (gl/cr), language (hl/lr), device type, and page-based pagination. Supports Google's advanced filters (tbs). Returns video title, thumbnail, duration, source platform, channel/creator, direct video URL, the platform's video ID and profile handle, and ready-to-call HasData API links (hasdataLinks) for the video's comments, transcript, profile, posts or channel. Use for short-form content discovery, viral-trend monitoring, influencer research, cross-platform video aggregation, and sourcing short clips to summarize or embed in LLM responses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query term for retrieving short videos results.
crNoThe country code for the country you want to limit the search to. Provide one exact documented value (237 allowed), e.g. `countryAF`, `countryAL`.
glNoThe 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`.
hlNoThe 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`.
lrNoThe 'lr' parameter specifies the language of the websites to return results from. This parameter filters results based on the language of the web content.
tbsNoGoogle advanced search filters, combined with commas. For example: - `qdr:h`, `qdr:d`, `qdr:w`, `qdr:m`, `qdr:y` - Show videos from the past hour, day, week, month, or year.
pageNoPage number for paginated results, where 0 is the first page.
uuleNoThe encoded location parameter.
locationNoGoogle canonical location for the search.
deviceTypeNoSpecify the device type for the search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tbs
      Added value: +{
+  "description": "Google advanced search filters, combined with commas. For example:\n\n  - `qdr:h`, `qdr:d`, `qdr:w`, `qdr:m`, `qdr:y` - Show videos from the past hour, day, week, month, or year.\n",
+  "type": "string"
+}
  2. Changed6 schema fields changed
    • changedInput schema / properties / cr / description
      Previous value: -"The country code for the country you want to limit the search to."New value: +"The country code for the country you want to limit the search to. Provide one exact documented value (237 allowed), e.g. `countryAF`, `countryAL`."
    • removedInput schema / properties / cr / enum
      Removed value: -[
-  "countryAF",
-  "countryAL",
-  "countryDZ",
-  "countryAS",
-  "countryAD",
-  "countryAO",
-  "countryAI",
-  "countryAQ",
-  "countryAG",
-  "countryAR",
-  "countryAM",
-  "countryAW",
-  "countryAU",
-  "countryAT",
-  "countryAZ",
-  "countryBS",
-  "countryBH",
-  "countryBD",
-  "countryBB",
-  "countryBY",
-  "countryBE",
-  "countryBZ",
-  "countryBJ",
-  "countryBM",
-  "countryBT",
-  "countryBO",
-  "countryBA",
-  "countryBW",
-  "countryBV",
-  "countryBR",
-  "countryIO",
-  "countryVG",
-  "countryBN",
-  "countryBG",
-  "countryBF",
-  "countryBI",
-  "countryKH",
-  "countryCM",
-  "countryCA",
-  "countryCV",
-  "countryKY",
-  "countryCF",
-  "countryTD",
-  "countryCL",
-  "countryCN",
-  "countryCX",
-  "countryCC",
-  "countryCO",
-  "countryKM",
-  "countryCG",
-  "countryCD",
-  "countryCK",
-  "countryCR",
-  "countryCI",
-  "countryHR",
-  "countryCU",
-  "countryCY",
-  "countryCZ",
-  "countryDK",
-  "countryDJ",
-  "countryDM",
-  "countryDO",
-  "countryEC",
-  "countryEG",
-  "countrySV",
-  "countryGQ",
-  "countryER",
-  "countryEE",
-  "countrySZ",
-  "countryET",
-  "countryFK",
-  "countryFO",
-  "countryFJ",
-  "countryFI",
-  "countryFR",
-  "countryGF",
-  "countryPF",
-  "countryTF",
-  "countryGA",
-  "countryGM",
-  "countryGE",
-  "countryDE",
-  "countryGH",
-  "countryGI",
-  "countryGR",
-  "countryGL",
-  "countryGD",
-  "countryGP",
-  "countryGU",
-  "countryGT",
-  "countryGN",
-  "countryGW",
-  "countryGY",
-  "countryHT",
-  "countryHM",
-  "countryHN",
-  "countryHK",
-  "countryHU",
-  "countryIS",
-  "countryIN",
-  "countryID",
-  "countryIR",
-  "countryIQ",
-  "countryIE",
-  "countryIL",
-  "countryIT",
-  "countryJM",
-  "countryJP",
-  "countryJO",
-  "countryKZ",
-  "countryKE",
-  "countryKI",
-  "countryKW",
-  "countryKG",
-  "countryLA",
-  "countryLV",
-  "countryLB",
-  "countryLS",
-  "countryLR",
-  "countryLY",
-  "countryLI",
-  "countryLT",
-  "countryLU",
-  "countryMO",
-  "countryMG",
-  "countryMW",
-  "countryMY",
-  "countryMV",
-  "countryML",
-  "countryMT",
-  "countryMH",
-  "countryMQ",
-  "countryMR",
-  "countryMU",
-  "countryYT",
-  "countryMX",
-  "countryFM",
-  "countryMD",
-  "countryMC",
-  "countryMN",
-  "countryMS",
-  "countryMA",
-  "countryMZ",
-  "countryMM",
-  "countryNA",
-  "countryNR",
-  "countryNP",
-  "countryNL",
-  "countryNC",
-  "countryNZ",
-  "countryNI",
-  "countryNE",
-  "countryNG",
-  "countryNU",
-  "countryNF",
-  "countryKP",
-  "countryMK",
-  "countryMP",
-  "countryNO",
-  "countryOM",
-  "countryPK",
-  "countryPW",
-  "countryPS",
-  "countryPA",
-  "countryPG",
-  "countryPY",
-  "countryPE",
-  "countryPH",
-  "countryPN",
-  "countryPL",
-  "countryPT",
-  "countryPR",
-  "countryQA",
-  "countryRE",
-  "countryRO",
-  "countryRU",
-  "countryRW",
-  "countryWS",
-  "countrySM",
-  "countryST",
-  "countrySA",
-  "countrySN",
-  "countryRS",
-  "countrySC",
-  "countrySL",
-  "countrySG",
-  "countrySK",
-  "countrySI",
-  "countrySB",
-  "countrySO",
-  "countryZA",
-  "countryGS",
-  "countryKR",
-  "countryES",
-  "countryLK",
-  "countrySH",
-  "countryKN",
-  "countryLC",
-  "countryPM",
-  "countryVC",
-  "countrySD",
-  "countrySR",
-  "countrySJ",
-  "countrySE",
-  "countryCH",
-  "countrySY",
-  "countryTW",
-  "countryTJ",
-  "countryTZ",
-  "countryTH",
-  "countryTG",
-  "countryTK",
-  "countryTO",
-  "countryTT",
-  "countryTN",
-  "countryTR",
-  "countryTM",
-  "countryTC",
-  "countryTV",
-  "countryUM",
-  "countryVI",
-  "countryUG",
-  "countryUA",
-  "countryAE",
-  "countryGB",
-  "countryUS",
-  "countryUY",
-  "countryUZ",
-  "countryVU",
-  "countryVA",
-  "countryVE",
-  "countryVN",
-  "countryWF",
-  "countryEH",
-  "countryYE",
-  "countryZM",
-  "countryZW"
-]
    • 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"
-]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, open-world behavior, so the bar is lower. The description goes on to disclose the return surface (title, thumbnail, duration, source platform, channel, direct URL, platform video ID, profile handle) and the hasdataLinks follow-up capability, which is genuinely useful behavioral context. It omits rate limits and response envelope details, keeping it below a 5.

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?

The definition is front-loaded with the core action, then output, then use cases — a logical progression with no filler sentences. Length is proportionate to a 10-parameter tool with no output schema.

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?

With no output schema, the description takes on the burden of describing return fields, which it does thoroughly, and it covers the parameter envelope and intended use cases. An agent has everything needed to invoke it correctly.

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 the schema already documents all 10 parameters in detail and the baseline is 3. The description groups them (location/uule, country gl/cr, language hl/lr, device type, page pagination, tbs filters), which adds light interpretive structure but does not clarify the gl-vs-cr or hl-vs-lr distinction beyond what the schema already says.

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 states a specific verb and resource — scraping the Google Short Videos carousel (explicitly TikTok, YouTube Shorts, Instagram Reels) — which is concrete and distinguishable from the generic google_serp_serp_getSearchResults and platform-specific tiktok/youtube siblings. An agent can tell what this returns without opening the schema.

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 clear context for use (short-form content discovery, viral-trend monitoring, influencer research, cross-platform aggregation, sourcing clips for LLM summarization/embedding). It does not, however, state when NOT to use it or explicitly name alternatives such as the general SERP or TikTok search tools, so routing between overlapping siblings is left to inference.

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

All HasData toolsInspect
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