Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

shein_category_goods

Lists SHEIN category products by numeric cat_id with pagination and sorting, returning IDs, names, images, prices, ratings, reviews, and sale/sold-out flags.

Instructions

SHEIN category product listing. Lists products in a SHEIN category, by the required numeric cat_id. page starts at 1 and page_size is 1-20 (default 20); sort is a non-negative integer, 0 by default. Each product has its id, name, images, sale, retail and USD prices, rating, review count, and on_sale and sold_out flags. total is the category's listing count.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number
sortNoSHEIN sort code: a non-negative integer. `0` is the default (recommended). Other codes are accepted and forwarded as-is; the full code-to-meaning mapping has not been live-verified yet (see the endpoint markdown), so callers relying on a specific ordering should confirm behavior empirically.
cat_idYesNumeric SHEIN category id
page_sizeNoResults per page, 1-20 (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.16
    • changedInput schema / properties / page_size / description
      Previous value: -"Results per page"New value: +"Results per page, 1-20 (default 20)"
  2. Changed1 schema field changedv1.17.5
    • changedInput schema / properties / sort / description
      Previous value: -"SHEIN sort code"New value: +"SHEIN sort code: a non-negative integer. `0` is the default (recommended). Other codes are accepted and forwarded as-is; the full code-to-meaning mapping has not been live-verified yet (see the endpoint markdown), so callers relying on a specific ordering should confirm behavior empirically."
  3. Addedv1.16.0

TDQS

A3.8/5.0
Behavior4/5

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

No annotations exist, so the description carries the full disclosure burden, and it does useful work: it enumerates the returned fields (id, name, images, prices, rating, review count, on_sale/sold_out flags, total) and states pagination defaults. Missing only operational context like rate limits or sourcing/auth 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?

Front-loaded with the purpose in the first sentence, then parameters, then return shape. No filler and every clause contributes information.

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?

With no output schema and no annotations, the description compensates well by describing the returned product fields and the total count. Adequate for an agent to call and interpret results, missing only edge cases (empty categories, invalid cat_id behavior).

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%, so the schema already documents every parameter's type and defaults. The description's parameter statements (page starts at 1, page_size 1-20 default 20, sort non-negative default 0) restate the schema rather than adding meaning, so the baseline 3 is appropriate.

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+resource: 'Lists products in a SHEIN category, by the required numeric cat_id.' This tells an agent exactly what it does, though it never names or distinguishes sibling tools like shein_products_search, shein_category_filters, or shein_category_nav that could be confused with it.

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?

Usage is implied — the tool requires a cat_id, so the agent infers it must first obtain a category id. There is no explicit when-to-use vs alternatives guidance, no pointer to shein_categories for finding cat_id, and no exclusion of the search or filter tools.

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