Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

shopee_shop_info

Read-only

Get one Shopee shop's public profile by numeric shop id: name, description, avatar images, status, official-shop and Shopee-verified flags, shop-level rating_star, label ids, and mart/overseas-shipping flags. Use it after shopee_shops or a product card supplies a shop id; region selects the storefront (my, sg, id, th, vn, ph, tw, br, mx, co, or cl) and defaults to my. An unknown shop id returns 404 instead of a partial profile.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "shop_id": "<shop_id>"
    },
    "name": "shopee_shop_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoOptional Shopee storefront region: my, sg, id, th, vn, ph, tw, br, mx, co, or cl. Defaults to my.
shop_idYesRequired numeric Shopee shop id, for example 52784309.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/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 still adds real behavioral value by disclosing the error contract: an unknown shop id "returns 404 instead of a partial profile", which tells the agent not to expect a degraded response. It does not add much more, but with annotations carrying the rest, this is solid.

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 purpose, then usage, then region, then error behavior — a logical order with no filler. The field enumeration is long but each item is a distinct piece of returned data, so it earns its space; slightly dense but not padded.

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?

With annotations and an output schema present, the description needn't explain return shape, and it doesn't. It covers prerequisites, region scoping, defaults, and the 404 case — everything an agent needs to call it correctly. Only marginal things like rate limits or caching are absent, which is acceptable for a read-only lookup.

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 documented in the schema, so baseline 3 applies. The description restates the region list and default and stresses that shop_id must be numeric, but adds no format or edge-case guidance beyond what the schema already provides.

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 one Shopee shop's public profile by numeric shop id") and then enumerates exactly what fields come back (name, description, avatars, status, official/verified flags, rating_star, labels, mart/overseas flags). This clearly separates it from the sibling shopee_shops (a search/list) and from product tools.

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?

Explicitly tells the agent when to reach for it: "after shopee_shops or a product card supplies a shop id", naming the upstream tool that produces the required id. The region parameter's role and default ("defaults to my") are also stated, so invocation context is unambiguous.

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

All Crawlora MCP toolsInspect
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