Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

shopee_search_hints

Fetches server-ranked Shopee keyword hints for a given prefix via a credential-free endpoint, returning hint-panel keywords with rank and category metadata for search optimization.

Instructions

Get Shopee keyword hints. Returns server-ranked keyword hints for a prefix from the credential-free api/v4/search/search_hint JSON (distinct from search-suggestion: hint-panel keywords with rank/category metadata). Public, credential-free endpoint.

Input Schema

NameRequiredDescriptionDefault
regionNoShopee region: my, sg, id, th, vn, ph, tw, br, mx, co, cl (default my)
keywordYesKeyword prefix
versionNoHint protocol version: 1 or 2 (default 2)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and discloses key behavioral traits: the endpoint is public and credential-free, results are server-ranked, and the output is hint-panel keyword data with rank/category metadata. It omits rate limits and error behavior, but covers auth, read nature, and return character well for a simple lookup.

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?

The description is short and front-loaded: purpose first, then return and sibling distinction, then auth context. The final sentence repeats 'credential-free,' which is minor redundancy but does not significantly hurt readability.

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 simple read-only hint lookup with full schema description coverage and no output schema, the description provides enough context: public/credential-free access, server-ranked return values, and differentiation from search-suggestion. A more detailed return shape would be nice, but it is not essential here.

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 the schema already documents keyword, region enum, and version. The description adds only the notion of a 'prefix' and does not elaborate on region sensitivity or version differences, making this a baseline case where the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Get Shopee keyword hints' and 'Returns server-ranked keyword hints for a prefix.' It also distinguishes this tool from a plausible sibling, search-suggestion, by noting that these are hint-panel keywords with rank/category metadata.

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?

The description gives clear selection context by contrasting this tool with search-suggestion and describing the distinct output type. It does not provide explicit when-to-use/when-not-to-use rules or name other Shopee siblings, but the distinction is strong enough for most selection decisions.

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