Fetch Shopee search landing prefills and trending cards for a specified region to populate search suggestions.
Get Shopee search landing prefills. Returns Shopee's search-landing prefill/trending cards from the credential-free api/v4/search/search_prefills JSON. Public, credential-free endpoint.
| Name | Required | Description | Default |
|---|---|---|---|
| region | No | Shopee region: my, sg, id, th, vn, ph, tw, br, mx, co, cl (default my) |
Changes observed during successful MCP inspections.
v1.17.18Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description does carry the key behavioral fact an agent needs: the endpoint is public and credential-free, so no auth setup is required. It says nothing about rate limits, response size, or whether results are region-locale dependent beyond the parameter.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, front-loaded with the purpose, and no filler. Mild redundancy in saying 'credential-free' twice ('credential-free ... JSON' then 'Public, credential-free endpoint'), which costs it a point.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
A single optional parameter and no output schema means the description only needs to convey what is returned and whether auth is needed, and it does both. Missing only sibling disambiguation, which is the one real gap for an agent choosing among Shopee tools.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the region enum already lists all eleven markets plus the 'my' default, so the description adds no parameter meaning. Baseline 3 applies when the schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource (get Shopee search landing prefills) and clarifies the payload is prefill/trending cards from the search_prefills endpoint. It does not differentiate from near-neighbour siblings like shopee_suggest or shopee_search_hints, which an agent could easily confuse with this.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No statement of when to use this versus shopee_suggest, shopee_search_hints, or shopee_home. The agent must infer from the name alone that this is a landing-page content feed rather than query autocomplete.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.