Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

shopify_sitemap_urls

List Shopify storefront sitemap URL entries filtered by type—products, collections, pages, blogs, or all—with configurable limits up to 250.

Instructions

List Shopify sitemap URLs. Lists URL entries from a Shopify storefront's sitemaps, for the required url. type filters (all by default, products, collections, pages, blogs, agentic_discovery, other) and limit caps entries (default 50, max 250). Each has loc, type, handle, lastmod, changefreq and optional images.

Input Schema

NameRequiredDescriptionDefault
urlYesShopify storefront URL
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. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses defaults (type=all, limit=50, max 250) and the returned entry fields, which is useful, but says nothing about permissions/auth needs, pagination beyond the cap, or error behavior for invalid storefront URLs.

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 sentences, front-loaded with the core action, then parameters, then return shape. It is efficient, though the parameter recap partially duplicates the schema rather than adding new information.

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?

There is no output schema, so the description's enumeration of entry fields (loc, type, handle, lastmod, changefreq, optional images) usefully fills that gap. The main omission is sibling differentiation and any failure-mode guidance.

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 the schema already documents url, type, and limit. The description restates the type enum values and the limit defaults/max, adding no syntax or format detail beyond the structured fields. Baseline 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 gives a specific verb and resource ('List Shopify sitemap URLs') and elaborates that it lists URL entries from a storefront's sitemaps. However, it never distinguishes itself from the obvious sibling shopify_sitemaps, so an agent must open both to tell which returns sitemap index entries versus URL entries.

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?

It notes `url` is required, implying you need a storefront URL, but gives no when-to-use guidance and never mentions shopify_sitemaps as the alternative for enumerating sitemaps themselves. The agent is left to infer the routing.

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