Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rothys_sitemap_urls

Retrieve structured URL entries from Rothy's sitemaps by type, including loc, handle, lastmod, and images, with a configurable limit up to 250.

Instructions

List Rothy's sitemap URLs. Lists URL entries from Rothy's sitemaps for one type (all by default, or products, collections, pages, blogs, agentic_discovery, other), up to limit entries (default 50, max 250). Each has loc, type, handle, lastmod, changefreq and optional images.

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. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / type / enum
      Added value: +[
+  "all",
+  "products",
+  "collections",
+  "pages",
+  "blogs",
+  "agentic_discovery",
+  "other"
+]
  2. Addedv1.16.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully enumerates the returned fields (loc, type, handle, lastmod, changefreq, optional images), which substitutes for the missing output schema, but it discloses nothing about authentication, rate limits, or ordering, so it is only partially complete.

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?

Two tightly written sentences, with the core action front-loaded and the filter/limit constraints following. Minor redundancy in re-listing the enum values that already live in the schema, but nothing is wasted.

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?

For a simple read-only list tool with two well-documented parameters and no output schema, the description is close to complete because it names the fields each entry contains. The main gap is the absence of any routing hint relative to rothys_sitemaps.

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 both parameters are already documented in the schema, and the description largely repeats the enum values and the 50/250 limit bounds. It adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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?

The description states a specific verb and resource ('List Rothy's sitemap URLs') and defines scope via the type filter. It is clear what the tool does, but it never distinguishes itself from the sibling rothys_sitemaps, leaving the agent to infer the difference between listing sitemaps versus listing URLs within them.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of alternatives, even though rothys_sitemaps is an obvious sibling. The agent gets no help deciding whether it should call this tool or the sitemaps tool first.

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