Crawlora MCP

shopee_shops

Read-only

List one page of Shopee Mall's official-shop directory for a storefront: shop ids, usernames, display names, brand names, logos, and the total shop count. Use limit 1-100 (default 20) and zero-based offset; an offset equal to total returns an empty page. Use shopee_shop_info to resolve one shop id's full profile. region selects the storefront (my, sg, id, th, vn, ph, tw, br, mx, co, or cl) and defaults to my.

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_shops"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Optional number of shops to return, 1-100. 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.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 genuinely useful behavioral detail beyond that: fixed page size bounds, zero-based offset semantics, the empty-page termination signal, and per-region storefront switching with a stated default. It does not mention rate limits or auth, but for a read-only listing that is a minor gap.

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?

Four sentences, front-loaded with what is returned before the operational constraints. The sibling routing sentence and the pagination edge case each carry real information; there is no filler.

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-value documentation is optional, yet the description still summarizes the payload. Combined with annotations covering read-only/open-world and the schema covering all three params, 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, offset, and region fully. The description restates the same ranges and the same region enum without adding new semantics such as ordering of results or whether offsets are stable across calls. 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 (List) and a precisely scoped resource (one page of Shopee Mall's official-shop directory for a storefront), then enumerates the returned fields. It explicitly contrasts itself with shopee_shop_info, so an agent can pick it out of the large Shopee sibling set without opening schemas.

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?

Gives explicit routing: use this to enumerate shops, use shopee_shop_info to resolve a single shop id's full profile. It also documents the pagination boundary condition (offset equal to total returns an empty page), which tells the agent when to stop paging.

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?