Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

shein_store

Retrieve a SHEIN store profile and its selling categories by store code. Use the returned category IDs to list each category's products.

Instructions

SHEIN store profile and categories. Returns a SHEIN store/seller profile — name, logo, follower count, seller label, store-type flags — plus the categories the store sells into, by the numeric store_code that product search/category/detail results already return. Use the returned category_id with /shein/store/products to list that category's products.

Input Schema

NameRequiredDescriptionDefault
store_codeYesNumeric SHEIN store code, as returned in product cards

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden, and it does disclose the returned payload fields (profile attributes plus the store's selling categories), which is the main behavioral fact an agent needs. It stops short of stating what happens for an invalid or unknown store_code, or any auth/rate-limit constraints.

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 sentences, all of which earn their place: what it returns, where the key comes from, and what to do next. The payload summary is front-loaded before the workflow hints.

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?

No output schema exists, so the description correctly enumerates the return contents and links the result to a sibling tool, which is enough for a one-parameter lookup. Missing only edge-case behavior for unknown store codes.

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 coverage is 100% and the schema already says 'Numeric SHEIN store code, as returned in product cards'. The description adds only the provenance chain (search/category/detail results) and reinforces that it is numeric, which is marginal beyond what the schema provides, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: returns a SHEIN store/seller profile (name, logo, follower count, seller label, store-type flags) plus the store's categories. The scope is unambiguous and an agent can tell it apart from shein_store_products or shein_categories without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells the agent where the input comes from ('the numeric store_code that product search/category/detail results already return') and names the follow-on call ('Use the returned category_id with /shein/store/products to list that category's products'). The selection path and the alternative are both spelled out.

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