Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

shopee_flash_sale

Retrieve the active Shopee flash-sale product window by region with limit/offset pagination from a credential-free JSON endpoint for campaign sampling.

Instructions

Get the Shopee flash-sale window. Returns the active flash-sale product window from Shopee's credential-free api/v4/flash_sale/flash_sale_get_items JSON. The window is a sampler of the active campaign, not a full catalogue enumeration. Public, credential-free endpoint.

Input Schema

NameRequiredDescriptionDefault
limitNoCards to return (1-60, default 20)
offsetNoPagination offset (0-based)
regionNoShopee region: my, sg, id, th, vn, ph, tw, br, mx, co, cl (default my)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description usefully discloses that the endpoint is public and credential-free and that it returns a sampler rather than a full enumeration. It still omits rate-limit behavior, pagination semantics, and error characteristics, leaving some behavioral burden on the schema and caller.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and concise, with the core purpose stated in the first sentence. It has minor redundancy around 'credential-free' but otherwise every sentence contributes useful context.

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 simple read-only endpoint with three optional parameters and no output schema, the description covers the resource, data source, authentication model, and sampling limitation. It is nearly complete, though it could say more about pagination behavior or expected return shape.

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%, so limit, offset, and region are already fully documented in the schema. The description does not add any parameter-specific meaning beyond the schema, matching the baseline for high-coverage schemas.

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 uses a specific verb and resource: 'Get the Shopee flash-sale window,' then clarifies it returns the active flash-sale product window. It also distinguishes the scope by saying the window is a sampler of the active campaign, not a full catalogue enumeration.

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 description implies usage by framing it as the active flash-sale window and warning that it is a sampler rather than a full catalogue. However, it does not explicitly state when to use this tool versus alternatives or name any sibling tool that should be chosen instead.

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