Skip to main content
Glama

Unwrangle Search

unwrangle_search
Read-onlyIdempotent

Search a retailer (Amazon/Target/Best Buy/Home Depot/...) by keyword. Returns product name, brand, price, rating, url, id. Example: unwrangle_search({ retailer: "amazon", search: "wireless earbuds", 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": {
      "page": 1,
      "search": "wireless earbuds",
      "_apiKey": "your-unwrangle-api-key",
      "retailer": "amazon"
    },
    "name": "unwrangle_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number of results (default 1).
searchNoSearch keywords, e.g. "wireless earbuds".
_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. 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, and open-world behavior, so the safety profile is covered. The description usefully adds the response shape (name, brand, price, rating, url, id), which is needed because there is no output schema. It says nothing about result counts, pagination limits, or rate limits, which is the remaining gap.

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?

Three tight sentences: purpose first, return fields second, example last — appropriately front-loaded. The example partially duplicates the schema's examples array, a minor redundancy that keeps it just short of a 5.

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 five-parameter read-only search with no output schema, the description covers the essentials: what is searched, where, and what comes back. Missing pagination and rate-limit behavior are the only notable absences.

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 every parameter including retailer slugs and _apiKey is already documented in structured data. The example invocation only restates values the schema's examples array already provides, adding no new meaning beyond it.

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 and resource — keyword search against a named set of retailers — and enumerates the returned fields, so the agent knows exactly what it gets. It does not name or distinguish itself from siblings like unwrangle_product or unwrangle_reviews, so the boundary must be inferred from the parameter shape.

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?

Usage is only implied: a keyword search is the natural first step when you have no product id. There is no explicit when-to-use versus when-not clause and no pointer to unwrangle_product for detail lookups, leaving the agent to infer routing from the description alone.

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.