Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

shopify_pages

List static pages from a Shopify storefront by URL, with paging and limit controls, returning handles, titles, URLs, content, and dates.

Instructions

List Shopify pages. Lists static pages from a Shopify storefront given by the required url, paged with page (from 1) and limit (default 50, max 250). Each has handle, title, url, plain-text content and dates. If transport_mode is ssr_embedded, items hold only handle, url and updated_at.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does a good job: it discloses the returned item shape (handle, title, url, plain-text content, dates) and a conditional behavioral mode (ssr_embedded yielding only handle, url, updated_at). It omits auth requirements and rate limits, but for a read/list operation the return-shape disclosure is substantive.

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 purpose and scope, with no filler. The trailing transport_mode sentence is useful behaviorally but introduces an undefined term, slightly weakening an otherwise tight structure.

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?

With no output schema and no annotations, the description correctly steps in to describe returned fields and conditional output, which is the right instinct. However, the unexplained transport_mode condition (not a settable parameter) leaves an agent unsure how to trigger that mode, so completeness has a real gap.

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 schema already documents url, page, and limit. The description largely repeats that (page from 1, limit default 50/max 250) rather than adding syntax or format detail, giving no lift beyond the schema. It also references a transport_mode value that is not among the declared parameters, which adds confusion rather than clarity.

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 pages') and clarifies these are 'static pages' from a storefront, which distinguishes them from product/collection siblings like shopify_products and shopify_collections. It does not, however, explicitly differentiate from the singular shopify_page sibling, so it stops short of full sibling routing.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as shopify_page (single page) or how this differs from other listing tools. The pagination details are parameter mechanics, not usage routing, so an agent gets no help deciding when this tool is the right choice.

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