Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

shein_search_keywords

Fetch trending search keywords shown in SHEIN's search box to discover shopper search interests and support keyword or product research.

Instructions

SHEIN trending search keywords. Returns the trending search keywords SHEIN shows in its search box. scene defaults to trendStoreChannel and word_type to 1. Each keyword has its word, word_id, type and from.

Input Schema

NameRequiredDescriptionDefault
sceneNoKeyword scene: 1-64 letters, digits or underscores. Only trendStoreChannel is verified.
word_typeNoKeyword type: a 1-3 digit number. Only 1 is verified.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.16
    • changedInput schema / properties / scene / description
      Previous value: -"Keyword scene (trendStoreChannel)"New value: +"Keyword scene: 1-64 letters, digits or underscores. Only trendStoreChannel is verified."
    • changedInput schema / properties / word_type / description
      Previous value: -"Keyword type (1)"New value: +"Keyword type: a 1-3 digit number. Only 1 is verified."
  2. Addedv1.16.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the returned keyword fields and default parameter behavior, but does not state that this is a read-only endpoint, nor does it mention rate limits, pagination, or authentication needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences with no filler. The purpose is front-loaded, followed by defaults and return-field details.

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 two-parameter read tool with no output schema, the description explains the purpose, parameter defaults, and returned keyword fields. It stops short of usage guidance relative to the sibling autocomplete tool, but otherwise provides enough context to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful default behavior beyond the schema: `scene` defaults to `trendStoreChannel` and `word_type` to `1`. The schema only says those values are verified, not that they are defaults.

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: returns SHEIN trending search keywords shown in the search box. The 'trending' qualifier implicitly separates it from autocomplete behavior, but no sibling tool is named explicitly.

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 purpose implies use for discovering trending queries, and default values are supplied for both parameters. However, there is no explicit when-to-use or when-not-to-use guidance and no named alternative such as shein_search_autocomplete.

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