Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fashionnova_sitemap_urls

Retrieve capped Fashion Nova sitemap URLs by type—products, collections, pages, blogs, or other—to gather structured storefront links for crawling or indexing.

Instructions

List Fashion Nova sitemap URLs. Returns capped URL entries from Fashion Nova's (https://www.fashionnova.com) child sitemaps matching the requested type. The storefront URL is fixed server-side.

Input Schema

TableJSON 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

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It discloses that results are capped, that only child-sitemap URLs are returned, and that the storefront URL is fixed server-side, which is meaningful for a simple read/list tool. It does not describe output format or failure behavior, but the core behavioral traits are covered.

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?

Two well-structured sentences with no filler. The purpose is front-loaded, and the second sentence adds only relevant behavioral context about child sitemaps, caps, and the fixed storefront URL.

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 two-parameter list tool with a type enum and limit already documented in the schema, the description is largely complete: it names the source, the filter, the cap, and the fixed configuration. It does not spell out the exact return entry format, but the output is described as URL entries, which is sufficient given the simplicity of the tool.

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 the baseline is 3. The description reinforces the 'type' filter by mentioning child sitemaps matching the requested type and hints at the limit via 'capped URL entries,' but it adds no new semantic detail beyond the schema.

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 first sentence states the verb and resource precisely: 'List Fashion Nova sitemap URLs.' The second sentence clarifies that it operates on child sitemaps and filters by requested type, which also distinguishes it from the sibling fashionnova_sitemaps tool.

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?

The description implies when to use it through the type filter and child-sitemap phrasing, but it never explicitly names alternatives like fashionnova_sitemaps, fashionnova_products, or fashionnova_pages, nor does it state when not to use this tool. Some guidance is implied, but no direct routing is provided.

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