Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

shopify_sitemaps

List the child sitemaps in a Shopify storefront's sitemap index by URL, returning each sitemap's location and inferred type.

Instructions

List Shopify sitemaps. Lists the child sitemaps in a Shopify storefront's sitemap index, for the required url. Each has a loc and a type (products, collections, pages, blogs, agentic_discovery or other) inferred from its URL. Localhost, private-network and credentialed URLs are rejected.

Input Schema

NameRequiredDescriptionDefault
urlYesShopify storefront URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does disclose real behavior: the return shape (a `loc` and a `type`) and the enum of inferred types, plus an input-rejection rule for localhost/private-network/credentialed URLs. It stops short of noting rate limits, auth requirements, or whether the type inference is heuristic.

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 action front-loaded and the rejection constraint last. Minor waste in the opening 'List Shopify sitemaps.' which restates the name before the more informative second sentence.

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 correctly compensates by naming the returned fields and enumerating the `type` values. It also covers the key input-validation behavior. What is missing is guidance on pagination or how the index relates to the sibling URL-listing 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 description coverage is 100% and there is a single parameter, so the schema already documents `url`. The description only restates that `url` is required and adds no format or example beyond 'Shopify storefront URL' in the schema. Baseline 3 applies.

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?

States a specific verb (List) and resource (Shopify sitemaps) and scopes it precisely to 'child sitemaps in a Shopify storefront's sitemap index', which distinguishes it from the sibling shopify_sitemap_urls that returns the URLs inside those sitemaps. An agent can tell what it gets without opening the schema.

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 only implied by the description of what is returned; there is no explicit when-to-use statement and no named alternative (e.g., shopify_sitemap_urls) for fetching the actual page URLs. Adequate but the routing decision is left to inference.

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