Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

shein_category_goods

Retrieve SHEIN product listings by category ID. Returns normalized product-card fields for each item, enabling category-based product discovery and data collection.

Instructions

SHEIN category product listing. Returns SHEIN's product listing for a category, with the same normalized product-card fields as product search.

Input Schema

TableJSON 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

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. Addedv1.16.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions the return fields ('normalized product-card fields') but does not describe pagination behavior, sorting, any side effects, error conditions, or authentication requirements. The brevity leaves significant behavioral aspects undisclosed.

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?

The description is concise (two sentences) and front-loaded with the purpose. The first sentence states the core function, and the second clarifies the output format, referencing a known sibling. There is no verbosity or redundant information; every sentence earns its place.

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

Completeness2/5

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

The description is incomplete for a tool with no output schema and no annotations. It fails to explain pagination (page/page_size), sorting (sort parameter behavior), or the exact structure of 'normalized product-card fields'. Comparable sibling tools like shein_category_filters or shein_products_search are not referenced for disambiguation. An agent would need additional context to use this effectively.

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?

The description adds no parameter-specific meaning beyond what the input schema already provides (e.g., page, sort, cat_id, page_size all have descriptions). Since schema coverage is 100%, the baseline score of 3 applies. The description's mention of output format does not clarify parameters further.

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?

The description clearly states the tool returns SHEIN's product listing for a specific category, and explicitly references 'the same normalized product-card fields as product search', which distinguishes it from search-based siblings. The verb (Returns) and resource (product listing for a category) are clear, making the purpose unambiguous.

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

Usage Guidelines2/5

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

The description provides no explicit guidance on when to use this tool versus alternatives like shein_products_search or shein_category_filters. It only says it returns category-based listings and mentions the output format is like search, but does not state conditions, exclusions, or provide any comparative context.

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