Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

wish_product_reviews

Read-only

A Wish product's normalized customer reviews. id is taken from a search result's product_id field or a product page's URL. A product with zero reviews returns a normal, empty result rather than an error. A caller wanting more reviews should re-request with a larger count -- this does not support an offset/cursor parameter, since the upstream source does not support one.

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": {
      "id": "<id>",
      "count": "<count>"
    },
    "name": "wish_product_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesWish product id, a 24-character hex id from a search result's product_id field
countYesNumber of reviews to return, 1 to 200, defaults to 10

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / count / description
      Added value: +"Number of reviews to return, 1 to 200, defaults to 10"
    • addedInput schema / properties / id / description
      Added value: +"Wish product id, a 24-character hex id from a search result's product_id field"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses meaningful behaviors: zero-review products return an empty result rather than an error, and there is no offset/cursor support because upstream does not provide one. That pagination limitation is exactly the kind of non-obvious trait annotations cannot convey.

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?

Four sentences, front-loaded with the resource definition and no filler. Each sentence carries distinct information (identity, id source, empty-result behavior, pagination constraint), though it is slightly longer than strictly necessary.

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 an output schema present, return-value detail is not required, and the description covers the key edge cases an agent needs: id provenance, empty results, and the absence of pagination. Complete enough for a two-parameter review-fetch tool, with only minor room for more explicit sibling routing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents both parameters and the baseline is 3. The description still adds value by clarifying the id's provenance (search result product_id field or product URL) and the remedy for wanting more reviews (raise count), reinforcing the count semantics beyond the schema's '1 to 200, defaults to 10'.

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 names a specific resource ('A Wish product's normalized customer reviews'), so an agent immediately knows this returns reviews rather than the product itself, distinguishing it from wish_product and wish_product_related. It lacks an explicit verb and never names a sibling, but the resource scope is unambiguous.

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?

It tells the caller how to obtain the id (from a search result's product_id field or a product page URL) and how to get more reviews (re-request with a larger count). No sibling alternative is named, but the 'how to call it' context is clear and actionable.

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

All Crawlora MCP toolsInspect
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