HasData

google_serp_ai_mode: GET /

hasdata_google_serp_ai_mode_getAiModeResponse

Read-only

Get AI Mode SERP Results

Captures Gemini-powered AI Mode answers from Google Search. Returns the conversational response text, cited source links, subtopic breakdowns, and, when continuable is set, a subsequentRequestToken for multi-turn continuation. Use for next-gen search interfaces, AI-answer monitoring, citation tracking, content research agents, building question-answering pipelines grounded in live Google results, and person/company data enrichment — e.g. asking Who is the CEO of HasData?, What is Roman Milyushkevich's LinkedIn?, HasData founder email, HasData Instagram handle to get a synthesized answer plus source URLs in one call, ideal for lead enrichment, sales research, people search, and filling in contact/attribute gaps for CRM records.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	Yes	Specify the search term for which you want to scrape the SERP.
`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`.
`uule`	No	The encoded location parameter.
`location`	No	Google canonical location for the search.
`continuable`	No	Whether to continue an existing AI Mode conversation.
`subsequentRequestToken`	No	Token used to continue a previous AI Mode 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"
-]

First observedApr 28, 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, open-world, non-destructive behavior, lowering the disclosure burden. The description adds useful behavioral detail beyond annotations: it returns conversational response text, cited source links, subtopic breakdowns, and a subsequentRequestToken when continuable is set for multi-turn continuation.

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 first two sentences are front-loaded and earn their place by specifying the operation and return fields. The remainder is an overlong, overlapping list of use cases and examples ('person/company data enrichment', 'lead enrichment, sales research, people search, and filling in contact/attribute gaps for CRM records') that bloats the definition without adding distinct decision value.

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

Completeness4/5

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

There is no output schema, so the description carries the return-value burden and mostly succeeds by naming the main response components. It does not cover error handling, authentication, or rate limits, but for a read-only scraping endpoint with fully documented parameters and clear safety annotations, this is close to complete.

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 description coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining the relationship between continuable and subsequentRequestToken for multi-turn AI Mode continuation, though it does not expand on q, gl, hl, uule, or location.

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: 'Get AI Mode SERP Results' and 'Captures Gemini-powered AI Mode answers from Google Search.' It clearly distinguishes the tool from generic Google SERP and AI Overview siblings by naming the AI Mode/Gemini conversational answer output.

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?

Provides clear usage contexts ('Use for next-gen search interfaces, AI-answer monitoring, citation tracking, content research agents...') and concrete examples like `Who is the CEO of HasData?`. It does not, however, name when-not-to-use it or explicitly route the agent to sibling alternatives such as ai_overview or regular SERP tools.

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?