Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rebag_sitemap_urls

List Rebag sitemap URL entries filtered by type or limit, returning canonical URLs, handles, lastmod dates, and image metadata.

Instructions

List Rebag sitemap URLs. Lists URL entries from Rebag's sitemaps, filtered by type (all, products, collections, pages, blogs, agentic_discovery or other; default all). Collection stops at limit entries (default 50, max 250). Each entry has loc, type, handle, lastmod, changefreq and, where present, images with caption, title and URL.

Input Schema

NameRequiredDescriptionDefault
typeNoSitemap type. Allowed values: all, products, collections, pages, blogs, agentic_discovery, other
limitNoMaximum URL entries, defaults to 50 and supports up to 250

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior4/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 well: it discloses that collection stops at `limit` (default 50, max 250), the default `all` filter behavior, and the per-entry fields including optional `images`. It omits auth requirements and rate-limit behavior, keeping it from a 5.

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?

Three tight sentences with the core purpose front-loaded. Minor redundancy between sentence one ('List Rebag sitemap URLs') and sentence two ('Lists URL entries from Rebag's sitemaps'), which restates the same idea before adding scope.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully enumerates the return fields (loc, type, handle, lastmod, changefreq, images with caption/title/URL) and covers filtering and pagination caps. Complete enough for an agent to call it, lacking only permission/auth details.

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% and both parameters are already documented with enums and defaults in the schema. The description restates the enum values and limit bounds without adding format, syntax, or edge-case meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List Rebag sitemap URLs') and scopes it to URL entries from Rebag's sitemaps, which is distinguishable from the sibling rebag_sitemaps. It does not explicitly name or contrast with rebag_sitemaps, so it falls short of a 5.

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

Usage Guidelines3/5

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

Usage is implied by the type filter and limit semantics, but there is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives like rebag_sitemaps. Adequate minimum for a straightforward list endpoint.

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