Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

shein_search_autocomplete

Get SHEIN search suggestions for a partial query to build autocomplete, returning each term's word, ID, and type. Pass a partial word; no matches return an empty list.

Instructions

SHEIN search autocomplete. Returns SHEIN search suggestions for a partial query in the required word. Each suggestion has its word, word_id and type. A word with no matching phrase returns an empty list, not an error.

Input Schema

NameRequiredDescriptionDefault
wordYesPartial search query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden, and it does add real value: it discloses the return shape (each suggestion has `word`, `word_id`, `type`) and, importantly, that an unmatched word yields an empty list rather than an error. It stops short of covering rate limits, auth, or ordering, so it is not fully complete.

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 short sentences with zero waste: purpose first, then return fields, then the edge-case behavior. Every sentence earns its place and the most important routing information is front-loaded.

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 single-parameter, annotation-free tool with no output schema, the description covers what the tool does, what it returns, and the empty-result edge case. It is nearly self-sufficient, with only the absence of alternative-tool routing keeping it from a 5.

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% and there is only one parameter, so the schema already documents `word` as a 'Partial search query'. The description reinforces that it must be partial and required, but adds no format, length, or language constraints beyond the schema. 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?

States a specific verb and resource: 'Returns SHEIN search suggestions for a partial query in the required `word`.' An agent can immediately tell this is an autocomplete/suggestion endpoint rather than a full product search. It does not explicitly distinguish itself from close siblings like shein_search_keywords or shein_products_search, which keeps it at a 4.

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 phrase 'for a partial query' implies the tool is meant for prefix/typeahead input rather than a full search, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative (e.g. use shein_products_search for full queries). Usage is inferable but not stated.

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