Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

shein_store

Read-only

Fetch a SHEIN store/seller profile (name, logo, followers, seller label, store-type flags) and the categories it sells into, by the store_code a product card carries. Use a returned category_id with shein_store_products; use shein_products_search or shein_products_detail to find or inspect store products.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "store_code": "<store_code>"
    },
    "name": "shein_store"
  }
}

Input Schema

NameRequiredDescriptionDefault
store_codeYesNumeric SHEIN store code, as returned in product cards

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real value by disclosing the shape of the payload (profile fields plus categories) and the provenance of the input, though it says nothing about freshness, throttling, or missing-store behavior.

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?

Two sentences, zero filler, payload description front-loaded and the cross-tool routing placed after it. Every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description needn't detail return structure, and it still names the key fields and follow-on tools. Nothing an agent needs to call this correctly against its SHEIN siblings is missing.

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?

Single parameter with 100% schema description coverage, so the schema already documents that store_code is a numeric SHEIN code from product cards. The description restates that provenance rather than adding format, range, or error semantics, so 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 (fetch) and resource (SHEIN store/seller profile), enumerates the returned fields (name, logo, followers, seller label, store-type flags, categories), and distinguishes itself from shein_store_products by using 'store' vs 'store products' framing.

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?

Explicit routing: 'Use a returned `category_id` with shein_store_products' and 'use shein_products_search or shein_products_detail to find or inspect store products.' It also implies the entry condition (you have a store_code carried on a product card).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources