Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

shopee_banners

Fetch Shopee homepage merchandising banners by region and banner slot from a credential-free public endpoint.

Instructions

Get Shopee homepage banners. Returns homepage merchandising banners for one slot from the credential-free api/v4/banner/batch_list_by_spaces POST JSON. Public, credential-free endpoint.

Input Schema

NameRequiredDescriptionDefault
slotNoBanner slot: HOME_CAROUSEL_01, HOME_SKINNY_01, HOME_NUZ_CAROUSEL_01, HOME_FLOATING, HOME_POPUP_01, HOME_MALL_01 (default HOME_CAROUSEL_01)
regionNoShopee region: my, sg, id, th, vn, ph, tw, br, mx, co, cl (default my)
space_keyNoRaw PC-<CC>-<SLOT> space key override

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 full load and does disclose the key traits: it is a public, credential-free read, backed by a specific POST JSON endpoint, and returns exactly one slot per call. It omits rate limits, pagination and the shape of the returned banner objects.

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 purpose before the implementation detail. The first two sentences are somewhat redundant ('Get... banners' / 'Returns... banners'), but nothing is padding that harms comprehension.

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 3-param tool with no output schema and no annotations, the description covers the access model and slot granularity but says nothing about what a banner record contains (image URL, link target, ordering) — information the agent cannot get from structured fields here.

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 slot, region and space_key are already fully documented with enums and defaults. The description only adds the 'one slot per call' constraint, which is marginal beyond the schema baseline.

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 ('Get Shopee homepage banners') and narrows scope to homepage merchandising banners for a single slot. It is distinguishable from siblings like shopee_home or shopee_flash_sale, though it never names an alternative explicitly.

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 only implied: the agent can infer it should call this when it wants homepage banner assets. There is no statement of when to prefer shopee_home or shopee_home_categories instead, and no exclusions or prerequisites beyond 'credential-free'.

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