Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jumia_sitemap_urls

Read paginated URLs from a Jumia sitemap file for a selected country, returning each URL with its last-modified date and first image plus the file’s total URL count.

Instructions

Read the URLs in a Jumia sitemap file. Returns one page of the URLs listed in a Jumia sitemap file, each with its last-modified date and first image, plus the total number of URLs in the file. A product file holds up to 16,000 product URLs; page through it with page and page_size (up to 5000). Take the file name from jumia-sitemaps. A page past the end returns an empty list. 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 page of URLs
countryYesJumia country storefront
sitemapYesSitemap file name from jumia-sitemaps
page_sizeNoURLs per page

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?

With no annotations, the description carries the full burden and does so: it discloses the ~50s latency, the intermittent anti-bot 503 and the retry instruction, the empty-list behavior past the last page, and the 16,000-URL file ceiling. These are operational facts an agent could not obtain 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 return shape before paging and anti-bot caveats, so an agent gets the essentials first. The prose is dense but every sentence carries operational content; only the return-shape and paging sentences lightly overlap.

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 explain results and does: per-URL last-modified date and first image, plus the total URL count. Combined with paging limits and failure/retry behavior, an agent has everything needed to call and consume this correctly.

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 exceeds it by adding a page_size ceiling of 5000 and the ~16,000-URL product-file ceiling that the schema's 'URLs per page' does not convey. It also reinforces where sitemap and country values must come from.

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?

Names a specific verb and resource ('Read the URLs in a Jumia sitemap file') and immediately disambiguates from the sibling that lists files: 'Take the file name from jumia-sitemaps.' An agent can distinguish this from jumia_sitemaps without opening either schema.

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 to the siblings: file names come from jumia-sitemaps, valid country values from jumia-countries. It also states how to walk the file (page/page_size) and the per-call cap, leaving nothing to inference about when and how to use it.

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