Skip to main content
Glama

CrawlerData: Google Shopping & SERP

Google Shopping search

google_shopping_search
Read-only

Search Google Shopping. Returns products with title, price, merchant, rating, product_id and offer_id (use product_id, or offer_id when there is no product_id, with google_shopping_sellers; product_id with google_shopping_product). Optional city-level location. 1 credit.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "google_shopping_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoSearch from a point: its latitude in degrees, e.g. 40.7580. Give lat and lng together, instead of location or uule; set country to the point's country (default "us").
lngNoSearch from a point: its longitude in degrees, e.g. -73.9855. Give lat and lng together.
pageNo
uuleNoAdvanced: a raw Google uule value ("w+...", "a+...", "j+..."), plain or URL-encoded as copied from a Google URL. Use location instead unless you already have uule values.
queryYes
countryNoTwo-letter country code. Defaults to "us", or to the country of location.
languageNoen
locationNoSearch from a city, region or postal code: a Google canonical location name, "City,Region,Country" (Google Ads geotarget format), e.g. "Austin,Texas,United States". When country is omitted it is taken from the location.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / lat
      Added value: +{
      +  "description": "Search from a point: its latitude in degrees, e.g. 40.7580. Give lat and lng together, instead of location or uule; set country to the point's country (default \"us\").",
      +  "maximum": 90,
      +  "minimum": -90,
      +  "type": "number"
      +}
    • addedInput schema / properties / lng
      Added value: +{
      +  "description": "Search from a point: its longitude in degrees, e.g. -73.9855. Give lat and lng together.",
      +  "maximum": 180,
      +  "minimum": -180,
      +  "type": "number"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / uule / description
      Previous value: -"Advanced: a raw Google uule value (\"w+...\", \"a+...\", \"j+...\"), sent as is. Use location instead unless you already have uule values."New value: +"Advanced: a raw Google uule value (\"w+...\", \"a+...\", \"j+...\"), plain or URL-encoded as copied from a Google URL. Use location instead unless you already have uule values."
    • removedInput schema / properties / uule / pattern
      Removed value: -"^[A-Za-z][+ ][A-Za-z0-9+/_=-]{4,1000}$"
  3. Changed2 schema fields changed
    • changedInput schema / properties / uule / description
      Previous value: -"Advanced: a raw Google uule value, sent as is. Use location instead unless you already have uule values."New value: +"Advanced: a raw Google uule value (\"w+...\", \"a+...\", \"j+...\"), sent as is. Use location instead unless you already have uule values."
    • changedInput schema / properties / uule / pattern
      Previous value: -"^[aw][+ ][A-Za-z0-9+/_=-]{4,1000}$"New value: +"^[A-Za-z][+ ][A-Za-z0-9+/_=-]{4,1000}$"
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds the meaningful extra that a call costs 1 credit and enumerates the returned fields. It stops short of explaining pagination depth or how many results a page yields, which matters for an open-world search.

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?

Three dense sentences with no filler: purpose first, return shape and ID routing second, location note and cost last. The parenthetical routing clause is compact yet unambiguous.

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?

No output schema exists, so the description correctly takes on the burden of naming return fields, and it adds cost and follow-up-tool mapping. The remaining gap is pagination and result-volume behavior for an 8-parameter open-world search, which an agent would need to page 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?

With 63% schema coverage, the schema already documents lat/lng/uule/country/location, while query, page and language carry no descriptions. The description's only added signal is "Optional city-level location," which roughly restates the location parameter already documented in the schema; it does not compensate for page or language being undocumented anywhere.

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 ("Search Google Shopping") and immediately defines the return shape: title, price, merchant, rating, product_id, offer_id. The ID routing to google_shopping_sellers and google_shopping_product makes it unmistakable how this tool differs from its siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives follow-up guidance (which ID feeds which sibling) and notes that location is optional, but never states when to choose this over google_search or google_local, nor any exclusions. Usage is implied by the return format rather than declared.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources