Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

shopee_footer

Retrieves Shopee footer layout for a selected region, returning help topics, company links, payment and logistics partners, social links, and app download details via a public endpoint.

Instructions

Get the Shopee footer layout. Returns the site footer/navigation layout (help topics, about, payment/logistics partners, social links, app download) from the credential-free api/v4/pages/get_footer_layout 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.9/5.0
Behavior4/5

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

With no annotations, the description must carry the behavioral load, and it does disclose the key traits: public, credential-free access and the exact upstream path (api/v4/pages/get_footer_layout). It does not describe caching, rate limits, or failure behavior, but for a static read-only layout endpoint the most decision-relevant trait (no auth needed) is stated.

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 purpose and content, with the endpoint path last. 'credential-free' appears twice (once in the main sentence, once in the closing fragment), which is a small redundancy but nothing structurally wasteful.

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?

A simple tool with one optional enum parameter and no output schema; the description enumerates the returned sections, so an agent knows what to expect. The only minor gap is silence on how `region` changes the payload, which the schema covers adequately.

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 single `region` enum (with its 'default my' note) is already fully documented in structured data. The prose adds nothing about region semantics — e.g. that the footer content is localized per region — so baseline 3 applies.

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?

Specific verb+resource ('Get the Shopee footer layout') followed by an enumeration of the content returned (help topics, about, payment/logistics partners, social links, app download). Siblings (shopee_banners, shopee_categories, shopee_home, etc.) are clearly distinct resources, so no ambiguity remains.

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 by the content list: an agent can infer it should call this when it needs footer navigation links. However, there is no explicit statement of when to prefer this over a sibling such as shopee_home or shopee_categories, and no exclusions or preconditions beyond 'public endpoint'.

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