Unstuck

Compare Shopping Prices

shopping_prices

Read-onlyIdempotent

Compare what stores charge for a product right now. Returns the Google Shopping listings with price, currency, seller and link. Listings are as Google shows them and can include used, refurbished, rental and bundle offers, so check the title and seller before treating a price as the going rate. Use it to check competitor pricing or find the going rate before buying or listing something. Price: $0.25 per successful call; failed calls are free.

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": {
      "product": "<product>"
    },
    "name": "shopping_prices"
  }
}

Input Schema

Name	Required	Description
`api_key`	No	Your Unstuck API key, if this connection has none. Leave empty to try free tools or to get a key and payment link.
`product`	Yes	The product to price, e.g. "sony wh-1000xm5".
`location`	No	Country or place, e.g. "United States". Default "United States" (or the connection's default location).

Output Schema

Name	Required	Description
`product`	Yes
`results`	Yes
`location`	Yes	Location the prices are for.
`balance_usd`	Yes	Remaining prepaid balance, USD.
`charged_usd`	Yes	Amount charged for this call, USD.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 4, 2026

addedInput schema / properties / api_key

Added value: +{
+  "description": "Your Unstuck API key, if this connection has none. Leave empty to try free tools or to get a key and payment link.",
+  "maxLength": 200,
+  "type": "string"
+}

First observedOct 4, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent and open-world, but the description adds information the structured fields cannot: listings can include used, refurbished, rental and bundle offers, so titles and sellers must be inspected before trusting a price, plus a per-call cost model ($0.25 per successful call, failed calls free).

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?

Four sentences, each doing distinct work: purpose, return shape, data-quality caveat, intended use, cost. The core purpose is front-loaded and nothing is redundant.

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 an output schema present, return values need not be re-explained, yet the description still sketches the payload. Combined with the cost note and the offer-quality caveat, an agent has everything needed to decide and invoke correctly.

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%, with product, location and api_key all documented including defaults and examples, so the schema carries the parameter burden. The description adds no location/product formatting guidance beyond what the schema already says, matching the baseline 3.

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 ('Compare') and resource ('what stores charge for a product right now') and immediately clarifies the return payload (Google Shopping listings with price, currency, seller, link). No sibling tool covers price comparison, so it is unambiguously distinct.

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?

Gives concrete usage contexts: checking competitor pricing or finding the going rate before buying or listing. However, it names no alternatives or conditions under which another sibling (e.g. web_search) would be preferable, so it falls short of an explicit when-not.

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

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