Skip to main content
Glama

CrawlerData: Google Shopping & SERP

Google Shopping sellers

google_shopping_sellers
Read-only

Every seller's offer for a Google Shopping product_id: merchant, price, shipping, total, availability, delivery, store link. For a google_shopping_search result with no product_id (a single-store listing), pass its offer_id instead. 1 credit per 10 sellers returned (min 1).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "google_shopping_sellers"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNous
languageNoen
offer_idNoThe offer_id of a google-shopping-search result. Use it for a single-store listing (a result with no product_id), or with product_id: when Google has no product page for that product_id, the offer is looked up instead.
product_idNoThe product_id of a google-shopping-search result. Give product_id, offer_id, or both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / offer_id
      Added value: +{
      +  "description": "The offer_id of a google-shopping-search result. Use it for a single-store listing (a result with no product_id), or with product_id: when Google has no product page for that product_id, the offer is looked up instead.",
      +  "pattern": "^\\d{5,30}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / product_id / description
      Added value: +"The product_id of a google-shopping-search result. Give product_id, offer_id, or both."
    • removedInput schema / required
      Removed value: -[
      -  "product_id"
      -]
  2. 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=true and openWorldHint=true, so the safe-read profile is covered. The description adds genuinely new behavioral context beyond that: cost ('1 credit per 10 sellers returned (min 1)') and the offer_id fallback path when Google has no product page. It stops short of describing pagination or result limits for high-seller products.

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 short sentences, front-loaded with what the tool returns, then the routing rule, then the cost. Nothing is redundant and no sentence could be dropped without losing information.

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?

With no output schema, listing the returned fields is exactly the right compensation, and the cost note covers billing impact. The gaps are around the optional country/language parameters and what happens if neither product_id nor offer_id is supplied (zero required params in the schema), which an agent could hit and would have to guess about.

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 50%, so two of four parameters (country, language) are undocumented in both schema and description. The description's offer_id guidance largely restates the schema's own offer_id description, and it adds nothing about how country/language affect merchant availability or pricing, so it only partially compensates for the coverage gap.

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 gives a specific verb and resource ('Every seller's offer for a Google Shopping product_id') and enumerates the returned fields (merchant, price, shipping, total, availability, delivery, store link). It implicitly distinguishes itself from google_shopping_search (this is post-search, per-product), but never explicitly contrasts with sibling google_shopping_product, leaving the seller-listing vs single-product distinction partly inferred.

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 a clear conditional rule: when a google_shopping_search result has no product_id (single-store listing), pass the offer_id instead. That is actionable usage guidance. It does not, however, say when to prefer this tool over the sibling product tool, so alternatives are only implicitly handled.

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