Retrieve SHEIN trending search keywords from the app's search box to identify popular shopper queries for product research and trend tracking.
SHEIN trending search keywords. Returns the trending search keywords SHEIN's app surfaces in its search box.
| Name | Required | Description | Default |
|---|---|---|---|
| scene | No | Keyword scene (trendStoreChannel) | |
| word_type | No | Keyword type (1) |
Changes observed during successful MCP inspections.
v1.16.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the basic return value and doesn't mention how the optional scene and word_type parameters affect results, nor what the output structure looks like.
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?
The description is two concise sentences with the key action front-loaded. The first sentence is somewhat redundant with the second, but there's no waste and it remains highly scannable.
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?
The tool is simple, but the description lacks essential context: what the returned data looks like, how the optional parameters influence results, and when an agent should reach for this instead of the many sibling search/keyword tools. No output schema or annotations exist to compensate.
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 description coverage is 100%, so the baseline is 3. The schema gives minimal hints ('trendStoreChannel', '1') but the description adds no further meaning about what these parameters control or whether they are needed.
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?
The description clearly states the tool returns SHEIN's trending search keywords from its app search box, giving a specific verb and resource. It distinguishes from siblings like shein_search_autocomplete through the term 'trending,' though it doesn't explicitly name alternatives.
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?
There is no guidance on when to use this tool versus related SHEIN tools or other keyword/suggestion tools. The description implies a use case (retrieving trending keywords) but provides no exclusions, prerequisites, or alternative routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.