ScrapeUnblocker

Scrape Google Shopping product listings

google_shopping

Read-only

Runs the Google Shopping vertical (udm=28) for q and returns the product cards as JSON: title, price, currency, currencyCode, originalPrice, discount, merchant, delivery, rating, reviewCount, image and Google's own ids for the product (productId, catalogId, offerId - stable across searches, for tracking one product). Set proxy_country/gl to target a market (prices/merchants are region-specific) and min_price/max_price to filter. One render returns the first page of products (v1). Note: Google Shopping exposes no per-product URL, so url is omitted. image is the product's thumbnail URL. Returns JSON. Billed like an API request; listing plugins bill one unit per result page they fetch, so keep max_results modest.

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": {
      "q": "<q>"
    },
    "name": "google_shopping"
  }
}

Input Schema

Name	Required	Description
`q`	Yes	Product search term, e.g. 'wireless headphones'.
`gl`	No	Market of search, ISO-2, e.g. 'us', 'de'. Sets prices/merchants. Default: us.
`max_price`	No	Maximum price filter (whole units, gl currency).
`min_price`	No	Minimum price filter (whole units, gl currency).
`max_results`	No	How many products to return (v1: first page). Default: 60.
`proxy_country`	No	Proxy country the request is sent from (ISO-2, e.g. 'US', 'DE'). Prices/merchants are market-specific.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedNov 4, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / max_price / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / max_price / minimum
```
Added value: +-9007199254740991
```
- addedInput schema / properties / max_results / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / max_results / minimum
```
Added value: +-9007199254740991
```
- addedInput schema / properties / min_price / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / min_price / minimum
```
Added value: +-9007199254740991
```
AddedOct 16, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Beyond the readOnly/openWorld annotations the description discloses substantive behavior: only the first page is returned in v1, no per-product URL exists so `url` is omitted, `image` is a thumbnail, and listing plugins bill one unit per result page fetched. Those are exactly the facts an agent needs to plan costs and avoid expecting a product link.

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 front-loads the action and the returned fields, then moves to parameter guidance, caveats and cost. The field enumeration is long but earns its place given there is no output schema; the trailing billing note is slightly tacked-on but relevant.

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 and no annotation detail on returns, the description compensates fully by defining the response shape, the missing `url`, the thumbnail nature of `image`, the first-page-only limitation, and the per-page billing model — nothing material for correct invocation is left out.

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 every parameter is already documented in the schema and the baseline of 3 applies; the description restates the market and price-filter parameters without adding syntax or edge-case detail beyond them, though its notes on why market selection matters are mildly useful.

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 names a specific verb and resource ("Runs the Google Shopping vertical (`udm=28`) for `q`") and enumerates exactly what comes back, so an agent can distinguish it from google_search, amazon_search or walmart_search without opening a schema.

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?

It gives operational guidance inside the call (set `proxy_country`/`gl` for a market, `min_price`/`max_price` to filter, keep `max_results` modest because of per-page billing) but never states when to choose this over the sibling shopping/search tools or when not to use it.

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

All ScrapeUnblocker tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?