Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

shopee_shop_info

Resolve a Shopee shop's public identity by shop ID and optional region. Returns clean JSON from a credential-free endpoint, so you can verify shop details without signed anti-content access.

Instructions

Resolve a Shopee shop identity. Returns one shop public identity from the credential-free api/v4/search/get_shop_info JSON (works without the anti-content-signed shop/get_shop_base). Public, credential-free endpoint.

Input Schema

NameRequiredDescriptionDefault
regionNoShopee region: my, sg, id, th, vn, ph, tw, br, mx, co, cl (default my)
shop_idYesNumeric Shopee shop id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it states the endpoint is public and credential-free, that no anti-content-signed shop/get_shop_base call is needed, and that only public identity fields are returned. It omits failure behavior for an invalid shop_id/region and any rate-limit notes.

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?

Purpose is front-loaded in the first sentence and the three sentences are short. Minor redundancy: 'credential-free' appears twice and the endpoint-internals clause is jargon-heavy, though it does convey real information.

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 simple two-parameter lookup this is mostly sufficient, but there is no output schema and the description only says 'public identity' without indicating what fields that comprises, so an agent cannot anticipate the response shape or whether it can supply names, ratings, or follower counts.

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 coverage is 100% and both parameters are fully documented, including the region enum and default, so the baseline of 3 applies. The description adds nothing about shop_id format or what region actually changes (per-market domain/response).

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?

Specific verb ('Resolve') and resource ('Shopee shop identity'), plus the scope constraint 'Returns one shop' which implicitly separates it from the sibling shopee_shops listing tool. It never names that sibling explicitly, though, so sibling differentiation is left to inference.

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?

Usage is implied: you already have a numeric shop_id and want its public identity. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g. shopee_shops for discovery, shopee_suggest for lookup by name), so an agent must infer the routing itself.

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