Skip to main content
Glama

Google Shopping Prices

google_shopping_prices
Read-onlyIdempotent

Searches Google Shopping and returns up to 20 product offers from many merchants (title, url, price, merchant, rating, reviews_count), localized by country and language. Use it to compare what different stores charge for a product. It does not return price history or stock levels, and is not for listings on one marketplace (use amazon_product, search_walmart or search_ebay). A search with no matches is charged; errors are not. Required: query.

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_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoZero-based results page, integer from 0: 0 is the first page, 1 the second, e.g. 1. Omit for the first page; each page is a separate charged call.
queryYesProduct search text, 1-500 characters, e.g. "running shoes size 42".
countryNoTwo-letter country code that localizes the shops and prices, e.g. "it" or "gb". Omit for the source default, us.
resultsNoMaximum products returned, integer 1-20, default 10, e.g. 5.
languageNoTwo-letter language code for the product text, e.g. "en" or "it". Omit for the source default, en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Two-letter country code used to localize shopping results."New value: +"Two-letter country code that localizes the shops and prices, e.g. \"it\" or \"gb\". Omit for the source default, us."
    • changedInput schema / properties / language / description
      Previous value: -"Two-letter language code for shopping result text."New value: +"Two-letter language code for the product text, e.g. \"en\" or \"it\". Omit for the source default, en."
    • changedInput schema / properties / page / description
      Previous value: -"Zero-based shopping result page number."New value: +"Zero-based results page, integer from 0: 0 is the first page, 1 the second, e.g. 1. Omit for the first page; each page is a separate charged call."
    • changedInput schema / properties / query / description
      Previous value: -"Product search query."New value: +"Product search text, 1-500 characters, e.g. \"running shoes size 42\"."
    • changedInput schema / properties / results / description
      Previous value: -"Maximum number of products to return."New value: +"Maximum products returned, integer 1-20, default 10, e.g. 5."
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already establish readOnly/openWorld/idempotent, and the description adds genuinely new operational context: capped at 20 offers, no price history or stock data, and the cost model where empty results are charged but errors are not. That billing disclosure is unavailable anywhere else in the structured fields, which is exactly the value-add this dimension rewards.

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 tight sentences: capability and payload first, the negative boundary second, billing/required-param fact last. No filler and nothing repeated from annotations.

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 compensates by enumerating the returned fields, and it covers locale behavior, result cap, cost model, and exclusions for a read-only search tool. Nothing an agent needs to decide or call correctly is missing.

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 coverage is 100% with per-parameter examples and enum explanations, so the schema carries the load. The description only echoes that query is required and mentions country/language localization, adding no syntax or edge-case detail beyond the schema. Baseline 3 applies.

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 ("Searches Google Shopping") and immediately enumerates the returned fields (title, url, price, merchant, rating, reviews_count) plus localization. It also differentiates from named siblings (amazon_product, search_walmart, search_ebay), so an agent can disambiguate 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 Guidelines5/5

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

Explicitly gives the use case ("compare what different stores charge for a product") and a negative boundary ("not for listings on one marketplace") with the exact alternative tools named. The billing rule ("no matches is charged; errors are not") further informs when to risk a call.

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