Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

jumia_category

Browse a Jumia category by slug to get product cards, the category's total count, and a next-page flag for a chosen country storefront. Use it to page through category listings.

Instructions

Browse a Jumia category. Browses one Jumia category listing by slug and returns the same product cards as jumia-search, plus the category's upstream total_count and a has_next flag. Take the slug from jumia-categories (top-level departments, or a department's sub-categories). Jumia serves at most 50 pages. 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
pageNo1-based result page, 1 to 50
countryYesJumia country storefront
categoryYesCategory slug from jumia-categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.4/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 return shape (product cards + total_count + has_next), the 50-page upstream cap, ~50 second latency from an anti-bot challenge, and that 503s are expected and should be retried. That is exactly the behavior an agent needs before calling.

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 and front-loaded: purpose first, then return shape, then dependencies, then operational caveats. The opening is slightly redundant ("Browse a Jumia category. Browses one Jumia category listing...") but no sentence is wasted.

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 3-parameter read tool with no annotations and no output schema, the description covers purpose, output fields, parameter sourcing, pagination limits, latency and error handling. Nothing an agent needs in order to call it correctly is missing.

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%, so all three parameters are already documented, including the page range 1-50 and the country enum. The description only restates provenance (slug from jumia-categories, country from jumia-countries) that the schema descriptions already convey.

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 ("Browse a Jumia category") and then differentiates the output from jumia-search: same product cards plus the category's upstream total_count and has_next flag. An agent knows exactly what this returns and how it differs from a search call.

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?

Prerequisites are explicit: take the slug from jumia-categories, country from jumia-countries. It implicitly contrasts with jumia-search by describing shared output, but never states the condition under which browse beats search, nor any exclusion, so it stops short of full alternative routing.

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