Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

shopee_banners

Read-only

Get the merchandising banners for one Shopee homepage slot: banner ids, campaign unit ids, images, target urls, and scheduling times. The upstream call is a POST JSON with an unvalidated CSRF header, so treat it as read-only merchandising data. slot defaults to HOME_CAROUSEL_01 and also accepts HOME_SKINNY_01, HOME_NUZ_CAROUSEL_01, HOME_FLOATING, HOME_POPUP_01, or HOME_MALL_01; space_key overrides slot and region selects the storefront (my, sg, id, th, vn, ph, tw, br, mx, co, or cl, default 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_banners"
  }
}

Input Schema

NameRequiredDescriptionDefault
slotNoOptional banner slot: HOME_CAROUSEL_01 (default), HOME_SKINNY_01, HOME_NUZ_CAROUSEL_01, HOME_FLOATING, HOME_POPUP_01, or HOME_MALL_01.
regionNoOptional Shopee storefront region: my, sg, id, th, vn, ph, tw, br, mx, co, or cl. Defaults to my.
space_keyNoOptional raw PC-<CC>-<SLOT> space key; takes precedence over slot when set.

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.4/5.0
Behavior5/5

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

The description adds meaningful behavioral context beyond the annotations: it says the upstream call is a POST JSON with an unvalidated CSRF header, yet the data should be treated as read-only merchandising data. That reconciles the POST transport with the readOnlyHint annotation and warns about the CSRF nuance.

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?

The description is front-loaded with purpose and behavior, then parameter details. It is somewhat dense and repeats schema-listed values, but every sentence contributes to understanding or safe use.

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?

The tool has only three optional parameters, an output schema, and annotations covering read-only/open-world behavior. The description fills the remaining gaps: slot defaults, region options, override precedence, and the POST/CSRF caveat.

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 fully documents slot, region, and space_key. The description restates the same defaults, accepted values, and precedence rules rather than adding new syntax or format guidance, so baseline 3 is appropriate.

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?

The description uses a specific verb and resource: 'Get the merchandising banners for one Shopee homepage slot.' It also lists the returned fields, so the agent knows this is not a general Shopee homepage or category tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly frames usage around one homepage slot, including the default slot and accepted alternatives, and explains that space_key overrides slot. It does not explicitly compare against sibling tools such as shopee_home, but the context is still clear enough to guide selection.

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