Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

lazada_product

Retrieve detailed product information from a Lazada storefront by item ID, including title, brand, description, image gallery, category, and variant options.

Instructions

Get a Lazada country storefront's product-detail page. Returns one Lazada country storefront's product-detail page: title, brand, full description, image gallery, category breadcrumb, and selectable variant properties. item_id (and, for a specific variant, sku_id) are the same ids the search, category-products, and home endpoints already return as item_id. Price is best-effort, read from the page's own display-tracking data rather than a dedicated pricing field; rating and review count are not available on this endpoint because Lazada fetches them client-side after the initial page load.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sku_idNoOptional Lazada sku id, for a specific variant.
countryNoLazada country storefront. Defaults to id.
item_idYesLazada item 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.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of disclosing behavior. It honestly discloses that price is 'best-effort' and sourced from display-tracking data, and that ratings/reviews are unavailable because they load client-side. This is valuable transparency about data quality and completeness. It doesn't mention potential errors or rate limits, but for a read-only endpoint the disclosed limitations are sufficient.

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 four sentences, each adding distinct information: purpose, returned fields, id relationship, and data limitations. It is front-loaded with the core purpose and then builds logically. No redundant or filler content—every sentence earns its place.

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 tool with 3 parameters, no output schema, and no annotations, the description is quite complete. It covers what the tool returns, how to identify items, and what data is unreliable or missing. The only minor gap is not stating whether the tool requires any authentication or has usage limits, but those are not typically expected for such endpoints. Overall, an agent has enough context to decide to call this tool and interpret the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with each parameter having a description. The description adds meaningful context beyond the schema by explaining that item_id (and sku_id) are the same identifiers returned by search, category-products, and home endpoints, which helps agents understand how to obtain them. It also implies the country default is 'id' without repeating it. This is a helpful addition over the schema alone.

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 tool's purpose: 'Get a Lazada country storefront's product-detail page.' It also enumerates the returned content (title, brand, description, image gallery, breadcrumb, variants), which distinguishes it from other Lazada endpoints like search or category listing tools. The mention that item_id is shared with search, category-products, and home endpoints further clarifies its role in the product data flow.

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 implies when to use the tool: when you have an item_id from other Lazada endpoints and need detailed product information. It also explicitly states a limitation: rating and review count are not available, so agents know not to use this for that purpose. However, it doesn't explicitly name an alternative for ratings or state 'use this when you need product details' as a directive, leaving the usage context slightly implicit.

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