Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jumia_sitemaps

List sitemap files for a Jumia storefront, including product, brand, category, and curated-page files with names, types, languages, last-modified dates, and URLs; optionally filter by type.

Instructions

List the sitemap files of a Jumia storefront. Lists the sitemap files a Jumia storefront publishes: product, brand, category and curated-page (mlps) files, each with its name, type, language, last-modified date and URL. Pass a returned name to jumia-sitemap-urls to read the URLs in it. Optionally narrow to one type. 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
typeNoOnly list one kind of sitemap
countryYesJumia country storefront

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full transparency burden and does so well: it discloses the anti-bot challenge, possible ~50-second latency, 503 responses, and the need to retry. It also lists the fields returned for each sitemap file.

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 front-loaded with the core purpose, then adds return fields, the follow-up tool, optional narrowing, and operational caveats in a logical order. Every sentence contributes useful context without excessive length.

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?

Given no output schema and no annotations, the description compensates by naming the returned fields, the next tool to use, the required country input, and the anti-bot latency/503 behavior. An agent has enough information to select and invoke the tool 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 description coverage is 100%, so the enum meanings and required country parameter are already documented in the schema. The description adds only that type is optional and points to jumia-countries for country values, which is useful but limited beyond the structured fields.

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 uses a specific verb and resource: 'List the sitemap files of a Jumia storefront,' then enumerates the file kinds and returned fields. It also distinguishes this tool from the sibling jumia-sitemap-urls by explaining that a returned name should be passed to that tool to read URLs.

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 gives clear usage context: discover sitemap files here, optionally narrow by type, then pass a returned name to jumia-sitemap-urls. It points to jumia-countries for the required country value, though it does not explicitly state when not to use this tool versus other Jumia content tools.

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