WebLens

search_shopping

Google Shopping product search. Returns products with prices, sellers, ratings, and links. Price: $0.005

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": "search_shopping"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum results to return
`query`	Yes	Search query

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 13, 2026
- changedInput schema / properties / query / example
```
Previous value: -"x402 payment protocol"New value: +"mechanical keyboard"
```
Changed9 schema fields changedOct 13, 2026
- addedInput schema / properties / limit / default
```
Added value: +10
```
- changedInput schema / properties / limit / description
```
Previous value: -"Number of results (default: 10, max: 20)"New value: +"Maximum results to return"
```
- addedInput schema / properties / limit / example
```
Added value: +10
```
- addedInput schema / properties / limit / maximum
```
Added value: +20
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- changedInput schema / properties / query / description
```
Previous value: -"Product search query"New value: +"Search query"
```
- addedInput schema / properties / query / example
```
Added value: +"x402 payment protocol"
```
- addedInput schema / properties / query / maxLength
```
Added value: +500
```
- addedInput schema / properties / query / minLength
```
Added value: +1
```
First observedAug 4, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the return contents (prices, sellers, ratings, links) and the $0.005 cost, but omits auth needs, rate limits, and pagination behavior.

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 purpose, then return values, then cost. There is no redundant or wasted text.

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 simple two-parameter search tool with full schema coverage and no output schema, the description adequately covers purpose, returns, and cost. It could be slightly more complete by clarifying result behavior or alternatives, but nothing critical 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 description coverage is 100%, so the schema already documents both query and limit. The description adds no parameter-level semantics beyond what the schema provides, making baseline 3 appropriate.

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?

States a specific resource and action: "Google Shopping product search." It clearly identifies the product-search domain and lists returned fields, but does not explicitly differentiate itself from sibling search tools such as search_web.

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 phrase "product search" implies when to use the tool for shopping-related queries, but there is no explicit guidance on when to prefer it over search_web or other sibling search tools, and no exclusions are stated.

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

All WebLens 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.