Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

shopee_shops

List Shopee official shops by region with limit and offset pagination, returning directory data from a public, credential-free endpoint.

Instructions

List Shopee official shops. Returns a page of the official-shop (mall) directory from the credential-free api/v4/official_shop/get_shops JSON. Public, credential-free endpoint.

Input Schema

NameRequiredDescriptionDefault
limitNoShops to return (1-100, 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

B3.4/5.0
Behavior3/5

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

With no annotations, the description does real work by disclosing that the endpoint is public and credential-free and that results are paged, which an agent needs to know before calling. It stops short of stating rate limits, whether the directory is exhaustive, or anything about the result shape beyond 'a page'.

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?

Three short sentences, front-loaded with the action, then the data source, then the access constraint. The only waste is restating 'credential-free' both at the end of sentence two and again in sentence three.

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

Completeness3/5

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

For a zero-annotation tool with no output schema, the description covers access (public, no credentials) and paging but says nothing about what a shop record contains or how many results the directory holds, leaving the agent unable to predict the response.

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 fully documented in the schema itself, and the description adds nothing about their semantics or interaction (e.g. how pagination terminates). 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 and resource ('List Shopee official shops') and adds that it is a paged directory of mall/official shops, which separates it from shopee_shop_info (single shop lookup). It never names a sibling explicitly, so an agent still has to infer the boundary rather than being told.

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 phrase 'official-shop (mall) directory' implies the browse/discovery use case, but there is no explicit when-to-use, when-not-to-use, or named alternative among the shopee_* siblings such as shopee_mall_categories or shopee_shop_info.

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