Skip to main content
Glama

Unwrangle Product

unwrangle_product
Read-onlyIdempotent

Product detail from a retailer (Amazon/Target/Best Buy/Home Depot/Walmart/...). Returns title, brand, price, rating, availability. Pass the product url (works for any retailer), or for Amazon pass id/asin. Example: unwrangle_product({ retailer: "amazon", url: "https://www.amazon.com/dp/B07ZPKN6YR", _apiKey: "your-key" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "https://www.amazon.com/dp/B07ZPKN6YR",
      "_apiKey": "your-unwrangle-api-key",
      "retailer": "amazon"
    },
    "name": "unwrangle_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoProduct id (Amazon ASIN), alternative to url. Amazon: pair with country_code.
urlNoProduct page URL (recommended, works across all retailers).
asinNoAlias for id (Amazon ASIN).
_apiKeyYesUnwrangle API key (get one at unwrangle.com, $10 / 10k credits).
retailerNoRetailer slug that selects the platform, e.g. "amazon", "walmart", "target", "bestbuy", "homedepot", "lowes", "wayfair", "costco", "samsclub", "chewy", "tesco", "currys". Defaults to "amazon".
country_codeNoOptional 2-letter country code (e.g. "us", "uk"). Defaults to "us" when using an id/asin.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"Unwrangle API key (get one at unwrangle.com — $10 / 10k credits)."New value: +"Unwrangle API key (get one at unwrangle.com, $10 / 10k credits)."
    • changedInput schema / properties / id / description
      Previous value: -"Product id (Amazon ASIN) — alternative to url. Amazon: pair with country_code."New value: +"Product id (Amazon ASIN), alternative to url. Amazon: pair with country_code."
    • changedInput schema / properties / url / description
      Previous value: -"Product page URL (recommended — works across all retailers)."New value: +"Product page URL (recommended, works across all retailers)."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive, and open-world safety profile. The description adds useful behavioral context by naming the retailer scope and listing the return fields, though it does not describe error behavior or response shape beyond those fields.

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?

The description is short, front-loaded, and wastes no words: it states the purpose, return fields, input options, and an example in that order. The example is useful rather than redundant.

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 read-only product lookup with full schema coverage and no output schema, the description gives enough context to call the tool correctly, including return fields and retailer coverage. It could be slightly more complete by mentioning limitations or error cases, but nothing essential 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 all six parameters are already documented in the schema. The description reinforces URL versus Amazon id/asin usage and gives an example, but adds limited meaning beyond what the schema already says.

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 clearly states that this tool retrieves product detail from a retailer and lists the returned fields, so the verb/resource is easy to infer. It does not explicitly distinguish itself from sibling tools such as unwrangle_search or unwrangle_reviews, leaving that differentiation implicit.

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 description gives practical guidance on passing a product URL versus Amazon id/asin, plus an example call. However, it does not explicitly state when to use this tool instead of alternatives like search or reviews, so usage is only implied by the purpose.

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.