Searchapi

Google Shopping Search

google_shopping_search

Read-only

Search for products on Google Shopping. Returns product listings with prices, sellers, ratings, and comparison shopping data. Use google_product tool with product_token to get detailed product information.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	Yes	Product search query. Required.
`gl`	No	Country code for pricing and availability (e.g., 'us'). Default: us.
`page`	No	Page number for pagination.
`sort_by`	No	Sort order for results.
`location`	No	Geographic location for localized results and pricing.
`condition`	No	Product condition filter.
`price_max`	No	Maximum price filter (e.g., '500' or '$500').
`price_min`	No	Minimum price filter (e.g., '100' or '$100').
`is_on_sale`	No	Filter for products on sale.
`is_free_delivery`	No	Filter for products with free delivery.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJun 10, 2026
- addedInput schema / $schema
```
Added value: +"https://json-schema.org/draft/2020-12/schema"
```
Changed4 schema fields changedApr 9, 2026
- removedInput schema / properties / is_free_delivery / enum
```
Removed value: -[
-  "true",
-  "false"
-]
```
- changedInput schema / properties / is_free_delivery / type
```
Previous value: -"string"New value: +[
+  "boolean",
+  "string"
+]
```
- removedInput schema / properties / is_on_sale / enum
```
Removed value: -[
-  "true",
-  "false"
-]
```
- changedInput schema / properties / is_on_sale / type
```
Previous value: -"string"New value: +[
+  "boolean",
+  "string"
+]
```
First observedFeb 18, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already flag this as read-only and open-world; the description adds observable behavior: it returns listing-level pricing, seller, rating, and comparison data)Skip and indicates a follow-up path. No hidden side effects or destructive behavior need disclosure.

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 front-loaded sentences cover scope, return type, and next step, with no repetition of schema content or filler.

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 tool with eight parameters and no output schema, the description provides adequate return-shape and follow-up guidance. Minor details like pagination behavior or regional result variations are left to the schema, which covers the parameter side.

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?

The input schema already documents all parameter meanings fully (100% coverage), so the description adds no new parameter-level semantics. The product_token pointer is useful but not a parameter of this tool.

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 opens with a specific verb + resource ('Search for products on Google Shopping'), states exactly what is returned (prices, sellers, ratings, comparison shopping data), and explicitly routes follow-up work to google_product with product_token.

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 context for using this tool and tells the agent when to switch to google_product for detailed results. It does not explicitly contrast with every sibling search tool, but the product-shopping scope is unambiguous enough.

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

All Searchapi 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?