Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jumia_product

Retrieve full Jumia product details from a product URL, including price, discount, availability, ratings, seller info, features, and specifications for commerce data extraction.

Instructions

Get a Jumia product. Returns one Jumia product: name, brand, sku, images, price in the storefront's currency with original price and discount, availability, rating and rating count, category path, seller (name, id, score, followers, shipping speed), description, key features and the specification table. Pass the url returned by jumia-search or jumia-category; the storefront country is taken from the URL host. Jumia sits behind an anti-bot challenge that clears on only some connections, so a call can take up to about 50 seconds and may return 503; retry it. A product id Jumia no longer serves returns 404.

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute Jumia product URL from a search or category result

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.8/5.0
Behavior5/5

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

No annotations exist, so the description carries full burden, and it delivers: anti-bot gating, up-to-50-second latency, possible 503 with an explicit retry instruction, and 404 for delisted ids. These are exactly the operational facts an agent needs and cannot get from the schema.

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?

Front-loaded with purpose and payload, followed by sourcing, then failure modes — a sensible order. The return-field enumeration is long, but with no output schema it is doing necessary work rather than padding.

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?

For a one-parameter, no-annotation, no-output-schema tool, nothing an agent needs is missing: it covers input provenance, what comes back, latency budget, and error/retry behavior.

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%, so the baseline is 3. The description adds a real semantic layer not in the schema: the storefront country is derived from the URL host, which affects which marketplace is queried, and it constrains the source of the URL to search/category results.

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?

States a specific verb and resource ("Get a Jumia product") and then enumerates exactly what one product record contains (name, brand, sku, price with discount, seller block, specs). This clearly separates it from jumia-search, jumia-category and jumia-reviews.

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

Usage Guidelines5/5

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

Explicitly routes the agent: "Pass the url returned by jumia-search or jumia-category" tells it to first call a sibling discovery tool, and the note that the country comes from the URL host tells it not to hunt for a country parameter. Retry-on-503 and 404-on-dead-id guidance are concrete operating instructions.

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