Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wish_search

Search Wish's product catalog by keyword with offset-based pagination. Returns price, currency, rating, review count, and merchant ID; no matches yield an empty result, not an error.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of results per page, 1 to 70, defaults to 30
queryYesSearch keyword
offsetNoResult offset, 0-based, defaults to 0, must be an exact multiple of count up to 3 * count

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does useful work: it discloses that pagination is offset-based, enumerates the returned fields (price, currency, rating, review count, merchant id), and clarifies that a no-match query returns an empty result rather than an error — a genuinely valuable edge-case disclosure. Missing auth/rate-limit context keeps it out of the top band.

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 short sentences, front-loaded with the purpose, then pagination, return fields, and the empty-result edge case. Each sentence carries information and there is no padding, though the return-field enumeration could be trimmed against a dedicated output schema (none exists here).

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 three-parameter search tool with no output schema, the description adequately covers what is returned and how empty results behave. The main gap is the absence of routing guidance among the many wish_* and other marketplace search siblings, but operationally it is sufficient.

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 schema already documents all three parameters, setting the baseline at 3. The description adds only the framing that pagination is 'real offset-based', which gives mild context for the offset parameter but no syntax or constraint detail beyond the schema.

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 products') and clarifies it searches Wish's product catalog by keyword. This distinguishes it from catalog-fetch siblings like wish_product and wish_categories by implication, but it never names those siblings or how it differs from them.

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 keyword-search framing implies when this tool applies, and the pagination note hints at iterative use. However, there is no explicit when-to-use versus wish_product, wish_suggest, or wish_categories, and no stated prerequisites, so usage must be inferred.

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

Deploy Server

Other Tools