Crawlora MCP

wish_search

Read-only

Search Wish's product catalog by keyword, with real offset-based pagination: normalized products with price, currency, rating, review count, and merchant id. A query with no matches returns a normal, empty result rather than an error.

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": {
      "query": "<query>"
    },
    "name": "wish_search"
  }
}

Input Schema

Name	Required	Description
`count`	No	Number of results per page, 1 to 70, defaults to 30
`query`	Yes	Search keyword
`offset`	No	Result offset, 0-based, defaults to 0, must be an exact multiple of count up to 3 * count

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 7, 2026

addedInput schema / properties / count / description

Added value: +"Number of results per page, 1 to 70, defaults to 30"

addedInput schema / properties / offset / description

Added value: +"Result offset, 0-based, defaults to 0, must be an exact multiple of count up to 3 * count"

addedInput schema / properties / query / description
```
Added value: +"Search keyword"
```

First observedOct 7, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior beyond that: 'real offset-based pagination' and the explicit guarantee that a zero-match query returns an empty result rather than an error, which preempts a common agent failure mode.

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?

Two tightly written sentences, front-loaded with what it searches and what it returns, followed by the edge-case guarantee. No filler.

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 details are optional, yet the description names the key normalized fields and covers the pagination and empty-result contract. It could have added cross-references to sibling tools, but nothing essential for correct invocation 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 coverage is 100%, so count/query/offset are fully documented in the schema, including the offset multiple-of-count constraint. The description's mention of 'real offset-based pagination' reinforces but does not extend the schema's semantics, so baseline 3 applies.

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 ('Search Wish's product catalog by keyword') and characterizes the result set, so it is clearly a keyword-search tool rather than a detail lookup. It does not name or differentiate against siblings like wish_product or wish_suggest, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance is given: nothing says to use this for discovery vs. wish_product for a known item id, or wish_suggest for autocomplete. The only conditional statement is about empty results, which is behavior, not usage routing.

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

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