Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

quince_sitemap_urls

List Quince sitemap URLs by type (products, collections, subcollections, pages) with an optional limit. Returns clean URLs with handles extracted from paths for product lookups.

Instructions

List Quince sitemap URLs. Returns capped URL entries from Quince's own sitemaps matching the requested type. Each entry's handle is populated from the URL's own path (tracking/variant query parameters stripped) -- for type products, this is directly the value quince-product's own handle parameter expects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoSitemap type. Allowed values: all, products, collections, subcollections, pages
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",
+  "subcollections",
+  "pages"
+]
  2. Addedv1.16.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden of disclosing behavior. It explicitly mentions that results are 'capped', that tracking/variant query parameters are stripped from URLs, and that for products the handle matches what quince-product expects. These are valuable behavioral disclosures. It does not mention auth, rate limits, or error handling, but the disclosed behaviors are significant and non-obvious.

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 two sentences with no filler. It leads with the primary action, then adds essential details about capping and handle extraction. Every sentence contributes value and the structure is efficient and front-loaded.

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?

Given the simple tool with two optional parameters and no output schema, the description covers the main functional aspects: it returns a capped list, strips query parameters, and clarifies the handle semantics for products. It does not describe pagination or any edge cases, but for a URL-listing tool this is reasonably complete. The absence of an output schema makes the description more important, but it covers the key return characteristics.

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?

The input schema already describes both parameters (type with allowed values, limit with default/max) with 100% coverage. The description adds minimal parameter-specific meaning beyond restating that entries match the requested type. The handle-population note is about output, not parameter semantics. Since schema covers the parameters, a baseline score of 3 is appropriate.

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 states a clear action and resource: 'List Quince sitemap URLs' and specifies it returns capped entries matching a requested type. It also adds a distinctive detail about handle extraction from URL paths, which helps differentiate it from other sitemap tools like quince_sitemaps or quince_product. The purpose is unambiguous.

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 provides contextual clues about when to use the tool (to retrieve sitemap URLs of a certain type) but does not explicitly mention alternatives or when not to use it. It does not reference sibling tools like quince_sitemaps or explain how this differs from other sitemap URL tools. The context is clear but exclusionary guidance is missing.

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