Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

shopee_suggest

Fetch Shopee search autocomplete suggestions for a keyword prefix by region, helping you discover relevant shopper queries from a public credential-free endpoint.

Instructions

Get Shopee search suggestions. Returns Shopee search autocomplete suggestions for a keyword prefix from the credential-free api/v4/search/search_suggestion JSON. Public, credential-free endpoint.

Input Schema

NameRequiredDescriptionDefault
regionNoShopee region: my, sg, id, th, vn, ph, tw, br, mx, co, cl (default my)
keywordYesSearch keyword prefix

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations provided, the description does real work: it declares the endpoint public and credential-free (so no auth is needed), identifies the underlying JSON endpoint, and confirms the return is autocomplete suggestions. It stops short of describing response shape, result limits, or error behavior, but the auth/safety disclosure is the most important trait for this tool.

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 short sentences with the core purpose front-loaded. There is mild redundancy between 'Get Shopee search suggestions' and 'Returns Shopee search autocomplete suggestions', but 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?

For a two-parameter, read-only lookup tool with fully documented parameters and no output schema, the definition covers purpose, source, auth requirements, and return type. Missing only secondary details like how many suggestions come back or region-specific behavior.

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%, with both the keyword and the region enum (including the 'default my' note) already documented in the schema. The description reinforces 'keyword prefix' but adds nothing about region behavior or multi-region differences, 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?

The description names a specific verb and resource — 'Get Shopee search suggestions' / 'Shopee search autocomplete suggestions for a keyword prefix' — which is unambiguous. It does not, however, distinguish this from nearby siblings such as shopee_search_hints or shopee_prefills, so an agent cannot tell from the text alone which of these autocomplete-ish tools to pick.

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 by 'for a keyword prefix' and 'search suggestions', which suggests it belongs in a typeahead/query-building flow. There is no explicit statement of when to use this versus shopee_search_filters, shopee_search_hints, or the full shopee search tool, and no when-not guidance.

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