Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

lazada_home

Fetch a Lazada country storefront's homepage feed, including flash-sale cards, featured category links, and official-stores carousel. Select a country (id, ph, th, my, vn, sg) to get structured JSON data for those sections.

Instructions

Get a Lazada country storefront's homepage feed. Returns one Lazada country storefront's anonymous homepage feed: current flash-sale product cards, featured category links, and (where shown) an official-stores carousel. Product-detail and free-text catalog pages are not included because Lazada's stateless routes currently return an anti-bot challenge on every country domain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryNoLazada country storefront. Defaults to id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / country / enum
      Added value: +[
+  "id",
+  "ph",
+  "th",
+  "my",
+  "vn",
+  "sg"
+]
  2. Addedv1.16.2

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the anti-bot limitation and the content returned, which is useful. However, it does not mention pagination, rate limits, authentication, or the response structure, so transparency is moderate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the core purpose, and every clause adds value: what is returned, what is excluded, and why. No redundancy or filler.

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 single-parameter tool with no output schema, the description covers the essentials: what it returns, what it excludes, and the reason for exclusion. It lacks explicit response structure details, but the enumerated components give sufficient context for an agent to call it correctly.

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% for the single parameter 'country', which already includes an enum and description. The tool description adds no extra meaning beyond the schema, so the baseline score of 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 clearly states the verb 'Get' and the resource 'Lazada country storefront's homepage feed', and enumerates the exact components returned (flash-sale cards, category links, carousel). It also explicitly excludes product-detail and catalog pages, distinguishing it from siblings like lazada_product and lazada_search without ambiguity.

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?

The description explicitly states that product-detail and free-text catalog pages are not included and explains why (anti-bot challenge), which serves as a clear exclusion criterion. However, it does not name specific alternative tools to use for those needs, so it stops short of full guidance.

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