Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

shopee_home

Retrieve Shopee's modular homepage feed—banners, category squares, campaigns, flash-sale cards, prefills, and live sessions—by region from a public, credential-free JSON endpoint.

Instructions

Get the Shopee homepage feed. Returns the modular homepage feed (banners, category squares, campaigns, flash-sale cards, prefills, live sessions) from Shopee's credential-free api/v4/native/homepage JSON. Public, credential-free endpoint.

Input Schema

NameRequiredDescriptionDefault
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

A3.7/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 burden and does disclose the key behavioral traits: it is a public, credential-free endpoint and names the underlying `api/v4/native/homepage` JSON source. It omits rate-limit, caching, and failure behavior, keeping it just short of a 5.

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 and the returned content. Minor redundancy: "credential-free" is stated twice (mid-paragraph and again in the closing sentence).

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?

For a one-parameter, no-annotation, no-output-schema tool, the description supplies what structured fields cannot: the module types in the response and the auth model. Nothing an agent needs to call it correctly is missing, though the enumeration could be tighter.

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 the single `region` enum already documents all valid values and the 'my' default. The description adds nothing about region semantics, so baseline 3 applies.

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 + resource ("Get the Shopee homepage feed") plus an enumeration of the modules returned (banners, category squares, campaigns, flash-sale cards, prefills, live sessions). This implicitly separates it from section-specific siblings like shopee_banners or shopee_flash_sale, though it never names them 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: an agent can infer this is the composite homepage fetch rather than a single-section call. There is no explicit "use this when..." guidance and no statement about when to prefer shopee_banners, shopee_prefills, or shopee_categories instead.

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