Skip to main content
Glama

HasData

by com.hasdata.mcp
OverviewDiscussionsAdmin

google_serp_product: GET /

hasdata_google_serp_product_getProductInformation
Read-only

Get Product Information

Pulls detailed product data from Google Shopping by productId with searchType (offers, specs, reviews) and rich filters (free shipping, used-condition, sort by price/total price/deals/seller rating, reviews count). Returns product title, images, price, ratings, specs, merchant offers (seller, shipping, condition, total price), and review text depending on searchType. Use for price intelligence, catalog enrichment, review mining, competitor spec comparison, and building shopping assistants that surface the cheapest or highest-rated offer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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`.
uuleNoThe encoded location parameter.
startNoThis parameter specifies the number of search results to skip and is used for pagination. For example, a value of 0 (default) indicates the first page of results, 10 refers to the second page, and 20 to the third page. This parameter is applicable only when `searchType=offers` is specified. For reviews pagination use `filter` parameter.
domainNoGoogle domain to use. Default is google.com. Provide one exact documented value (195 allowed), e.g. `google.ac`, `google.ad`.
filterNoFilter parameter for refining search results. Supports various filters for offers and reviews. Multiple filters can be passed using a comma. The available filters are: Offers filters: - `freeship:1`: Show only products with free shipping. - `ucond:1`: Show only used products. - `scoring:p`: Sort by base price. - `scoring:tp`: Sort by total price. - `scoring:cpd`: Sort by current promotion deals (special offers). - `scoring:mrd`: Sort by seller's rating. Reviews filters: - `rnum:{number}`: Number of results (100 is max).
locationNoGoogle canonical location for the search.
productIdYesThe product ID to get results for.
searchTypeNoParameter for fetching specific product information, such as 'offers', 'specs', or 'reviews'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / domain / description
      Previous value: -"Google domain to use. Default is google.com."New value: +"Google domain to use. Default is google.com. Provide one exact documented value (195 allowed), e.g. `google.ac`, `google.ad`."
    • removedInput schema / properties / domain / enum
      Removed value: -[
-  "google.ac",
-  "google.ad",
-  "google.ae",
-  "google.al",
-  "google.am",
-  "google.as",
-  "google.at",
-  "google.az",
-  "google.ba",
-  "google.be",
-  "google.bf",
-  "google.bg",
-  "google.bi",
-  "google.bj",
-  "google.bs",
-  "google.bt",
-  "google.by",
-  "google.ca",
-  "google.cd",
-  "google.cf",
-  "google.cg",
-  "google.ch",
-  "google.ci",
-  "google.cl",
-  "google.cm",
-  "google.co.ao",
-  "google.co.bw",
-  "google.co.ck",
-  "google.co.cr",
-  "google.co.id",
-  "google.co.il",
-  "google.co.in",
-  "google.co.jp",
-  "google.co.ke",
-  "google.co.kr",
-  "google.co.ls",
-  "google.co.ma",
-  "google.co.mz",
-  "google.co.nz",
-  "google.co.th",
-  "google.co.tz",
-  "google.co.ug",
-  "google.co.uk",
-  "google.co.uz",
-  "google.co.ve",
-  "google.co.vi",
-  "google.co.za",
-  "google.co.zm",
-  "google.co.zw",
-  "google.com",
-  "google.com.af",
-  "google.com.ag",
-  "google.com.ai",
-  "google.com.ar",
-  "google.com.au",
-  "google.com.bd",
-  "google.com.bh",
-  "google.com.bn",
-  "google.com.bo",
-  "google.com.br",
-  "google.com.bz",
-  "google.com.co",
-  "google.com.cu",
-  "google.com.cy",
-  "google.com.do",
-  "google.com.ec",
-  "google.com.eg",
-  "google.com.et",
-  "google.com.fj",
-  "google.com.gh",
-  "google.com.gi",
-  "google.com.gt",
-  "google.com.hk",
-  "google.com.jm",
-  "google.com.kh",
-  "google.com.kw",
-  "google.com.lb",
-  "google.com.ly",
-  "google.com.mm",
-  "google.com.mt",
-  "google.com.mx",
-  "google.com.my",
-  "google.com.na",
-  "google.com.ng",
-  "google.ng",
-  "google.com.nf",
-  "google.com.ni",
-  "google.com.np",
-  "google.com.om",
-  "google.com.pa",
-  "google.com.pe",
-  "google.com.pg",
-  "google.com.ph",
-  "google.com.pk",
-  "google.com.pr",
-  "google.com.py",
-  "google.com.qa",
-  "google.com.sa",
-  "google.com.sb",
-  "google.com.sg",
-  "google.com.sl",
-  "google.com.sv",
-  "google.com.tj",
-  "google.com.tr",
-  "google.com.tw",
-  "google.com.ua",
-  "google.com.uy",
-  "google.com.vc",
-  "google.com.vn",
-  "google.cat",
-  "google.cn",
-  "google.cv",
-  "google.cz",
-  "google.de",
-  "google.dj",
-  "google.dk",
-  "google.dm",
-  "google.dz",
-  "google.ee",
-  "google.es",
-  "google.fi",
-  "google.fm",
-  "google.fr",
-  "google.ga",
-  "google.ge",
-  "google.gg",
-  "google.gl",
-  "google.gm",
-  "google.gp",
-  "google.gr",
-  "google.gy",
-  "google.hn",
-  "google.hr",
-  "google.ht",
-  "google.hu",
-  "google.ie",
-  "google.im",
-  "google.iq",
-  "google.is",
-  "google.it",
-  "google.je",
-  "google.jo",
-  "google.kg",
-  "google.ki",
-  "google.kz",
-  "google.la",
-  "google.li",
-  "google.lk",
-  "google.lt",
-  "google.lu",
-  "google.lv",
-  "google.md",
-  "google.me",
-  "google.mg",
-  "google.mk",
-  "google.ml",
-  "google.mn",
-  "google.ms",
-  "google.mu",
-  "google.mv",
-  "google.mw",
-  "google.ne",
-  "google.nl",
-  "google.no",
-  "google.nr",
-  "google.nu",
-  "google.pl",
-  "google.pn",
-  "google.ps",
-  "google.pt",
-  "google.ro",
-  "google.rs",
-  "google.ru",
-  "google.rw",
-  "google.sc",
-  "google.se",
-  "google.sh",
-  "google.si",
-  "google.sk",
-  "google.sm",
-  "google.sn",
-  "google.so",
-  "google.sr",
-  "google.st",
-  "google.td",
-  "google.tg",
-  "google.tk",
-  "google.tl",
-  "google.tm",
-  "google.tn",
-  "google.to",
-  "google.tt",
-  "google.vg",
-  "google.vu",
-  "google.ws"
-]
    • 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"
-]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description usefully notes that the returned payload varies with searchType and enumerates the returned fields, but adds no auth, rate-limit, or pagination caveats beyond what the schema's 'start' description already supplies.

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?

It is three dense sentences that front-load the core action and then summarize inputs before closing with use cases. Every sentence contributes, though the parenthetical filter gloss in sentence one is slightly redundant with the schema and could be trimmed.

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?

For a nine-parameter read tool with full schema coverage but no output schema, the description does the necessary work of describing the return payload (title, images, price, ratings, specs, merchant offers, review text) and its dependence on searchType. What remains thin is the absence of any guidance on failure/empty cases, but overall it is sufficient for correct invocation.

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?

With schema description coverage at 100%, the schema already documents all nine parameters thoroughly, including enum values and the filter grammar. The description echoes the searchType values and filter categories (free shipping, used-condition, sort options) but introduces no syntax or semantics beyond what the schema provides, so the baseline 3 is appropriate.

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?

The description states a specific verb and resource: it 'pulls detailed product data from Google Shopping by productId,' which is a concrete scope. The 'by productId' phrasing implicitly distinguishes it from the search-oriented siblings like shopping_getSearchResults, but it never names those alternatives directly, so differentiation is inferred rather than stated.

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 usage context via concrete scenarios (price intelligence, catalog enrichment, review mining, competitor spec comparison, shopping assistants). However it offers no when-not conditions and never points the agent to a sibling tool, so selection between this and the shopping search tools 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