Skip to main content
Glama

Unwrangle Reviews

unwrangle_reviews
Read-onlyIdempotent

Reviews for a product on a retailer (Amazon/Target/Best Buy/...). Returns reviewer name, rating, title, text, date, verified-purchase flag. Pass the product url (or Amazon id/asin) and optional page. Reviews cost more credits than product/search. Example: unwrangle_reviews({ retailer: "amazon", url: "https://www.amazon.com/dp/B07ZPKN6YR", page: 1, _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",
      "page": 1,
      "_apiKey": "your-unwrangle-api-key",
      "retailer": "amazon"
    },
    "name": "unwrangle_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoProduct id (Amazon ASIN), alternative to url.
urlNoProduct page URL to fetch reviews for (recommended).
asinNoAlias for id (Amazon ASIN).
pageNoPage number of reviews (default 1).
_apiKeyYesUnwrangle API key (unwrangle.com).
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 (default "us").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Product id (Amazon ASIN) — alternative to url."New value: +"Product id (Amazon ASIN), alternative to url."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: the fields returned per review (reviewer name, rating, title, text, date, verified-purchase flag) and the credit-cost premium relative to product/search. It does not say how many reviews per page or whether pagination terminates, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Content is front-loaded: what it returns first, then how to call it, then the cost caveat, then an example. It is somewhat run-on and the example partially duplicates the schema's examples array, but no sentence is wasted.

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, the description compensates by enumerating returned review fields, and it covers the required _apiKey indirectly via the example and the url/id alternatives. Gaps remain around page-size, result limits, and behavior for unsupported retailers, but the essentials for a correct call are present.

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 baseline is 3: the schema already documents id, url, asin, page, retailer, country_code and _apiKey. The description reinforces the url-vs-id/asin choice and mentions page, but adds no format or default detail beyond what the schema states.

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 verb+resource: fetch reviews for a product on a named retailer, with concrete retailer examples and an inline call example. It is clearly distinct from unwrangle_product and unwrangle_search by resource (reviews vs product/search data), though it does not name those siblings explicitly.

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 tells the agent how to call it (pass url, or Amazon id/asin, plus optional page) and warns that reviews cost more credits than product/search, which implies a cost trade-off against alternatives. It never states explicitly when to prefer this over unwrangle_product or unwrangle_search, nor any exclusions.

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.