Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jumia_reviews

Fetch paginated written Jumia product reviews by SKU and country, including ratings, review text, dates, author first names, and a star-rating summary.

Instructions

Get the reviews of a Jumia product. Returns one page of a Jumia product's written, verified customer reviews (rating, title, text, date, first name of the author) with the rating summary: average rating, total ratings, total written reviews and the count of ratings per star. Reviews are 10 per page. A product with ratings but no written reviews returns an empty list with the summary. Pass the sku returned by jumia-search, jumia-category or jumia-product. 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. country is required; see jumia-countries.

Input Schema

NameRequiredDescriptionDefault
skuYesProduct sku
pageNo1-based page of reviews, 10 per page
countryYesJumia country storefront

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.6/5.0
Behavior5/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 so: it discloses the anti-bot challenge, calls taking up to ~50 seconds, possible 503 responses and an explicit retry instruction, plus the edge case that a product with ratings but no written reviews returns an empty list with the summary intact. That is exactly the operational context an agent needs.

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?

Dense but front-loaded: what it returns, then pagination, then the empty-result case, then parameter sourcing, then the latency/error warning. Almost every sentence adds information, though the return-field enumeration (rating, title, text, date, first name) is slightly list-heavy in an otherwise prose definition.

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?

No output schema exists, so the description must describe the return shape — and it does, listing review fields, the rating summary components and the empty-list behavior. Combined with pagination limits, sku provenance and the 503/retry guidance, nothing needed to invoke the tool correctly is missing.

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, but the description adds real value: page size of 10 (corroborating the page parameter's semantics), the origin of the sku argument, and the requirement that country be supplied with a reference to jumia-countries for the enum values.

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?

Opens with a specific verb+resource ("Get the reviews of a Jumia product") and immediately narrows scope to written, verified customer reviews plus the rating summary. That distinguishes it clearly from jumia_product, jumia_search and other Jumia siblings, which return catalog data rather than reviews.

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?

Explicitly tells the agent where the sku comes from (jumia-search, jumia-category, jumia-product) and that country is required with a pointer to jumia-countries. It covers the preconditions well but never states when NOT to use this tool, e.g. that jumia_product already surfaces the rating summary.

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