Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

shopify_collections

Fetch collections from a public Shopify storefront by URL to browse or analyze a store's catalog; use page and limit to control results.

Instructions

List Shopify collections. Returns collections from a public Shopify storefront. Valid empty result pages return 200 with an empty collections array.

Input Schema

NameRequiredDescriptionDefault
urlYesShopify storefront URL
pageNo1-based page, defaults to 1
limitNoMaximum collections, defaults to 50 and supports up to 250

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations, so the description carries the full burden. It does disclose two useful traits: results come from a public storefront (no auth) and valid empty pages return 200 with an empty array rather than an error. However, it says nothing about rate limits, overall pagination limits beyond the limit param, or the collection object shape.

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?

Three short, front-loaded sentences with no filler. The core purpose leads, and the empty-page behavior is stated compactly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description ideally would describe the returned collection shape, but it only mentions the empty-array case. For a low-complexity 3-param read tool this is adequate but leaves the return payload underspecified.

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, page (1-based, default 1) and limit (default 50, max 250). The description adds no parameter semantics beyond what the schema provides, so baseline 3 is appropriate.

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?

States a specific verb and resource ('List Shopify collections') and scopes it to a public storefront. The plural 'collections' vs the sibling 'shopify_collection_products' implies the distinction, but the description never names or contrasts a sibling explicitly, keeping it from a 5.

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?

No when-to-use guidance and no alternatives named. With siblings like shopify_collection_products, shopify_products and shopify_page, an agent gets no signal about which to pick or what prerequisite (a storefront URL) is required.

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