Crawlora MCP

shopee_flash_sale

Read-only

Get the live Shopee flash-sale window and its promotional product cards for one storefront: item ids, shop ids, names, prices, discounts, stock, ratings, and campaign start/end times. Treat it as a sampler of the current campaign, not a catalogue enumerator — the same offset can repeat cards and the campaign rotates on its own schedule. region selects the storefront (my, sg, id, th, vn, ph, tw, br, mx, co, or cl, default my); limit accepts 1-60 (default 20) and offset is zero-based.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "shopee_flash_sale"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Optional number of cards to return, 1-60. Defaults to 20.
`offset`	No	Optional zero-based pagination offset. Defaults to 0.
`region`	No	Optional Shopee storefront region: my, sg, id, th, vn, ph, tw, br, mx, co, or cl. Defaults to my.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover safety (readOnlyHint) and open-world scope, but the description adds genuinely non-obvious behavior: the campaign rotates on its own schedule and the same offset can repeat cards, so pagination is not stable. That is real operational context an agent cannot get from annotations. It stops short of 5 because freshness/caching and rate behavior are unstated.

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?

Front-loaded with the purpose and the key sampler caveat before the parameter clause, and every sentence carries information. The final clause re-enumerating schema defaults is mild redundancy that keeps it from a 5.

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?

An output schema exists, so return values need not be fully documented, yet the description still names the payload fields. Combined with the non-determinism warning and defaulted optional parameters, an agent has everything needed to call this correctly.

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 the schema already documents limit (1-60, default 20), offset (zero-based), and the full region enum with default. The description's closing sentence largely restates those facts rather than adding new meaning, 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 and resource ('Get the live Shopee flash-sale window and its promotional product cards') scoped to 'one storefront', and enumerates the returned fields (item ids, shop ids, prices, discounts, stock, ratings, campaign times). It also explicitly contrasts itself with a catalogue enumerator, which separates it from generic Shopee browsing siblings.

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

Usage Guidelines4/5

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

Explicitly tells the agent to treat the result as a sampler rather than an enumerator, which is actionable guidance about when not to keep paginating. It does not name a specific sibling to use instead (e.g. shopee_categories or shopee_search_hints) for full-catalogue needs, so it falls short of full alternative routing.

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

All Crawlora MCP tools Inspect

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

Need Help?