Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

shopify_page

Fetch a public Shopify storefront page by handle and store URL. Returns title, URL, timestamps, and plain-text content; unknown handles return 404.

Instructions

Get Shopify page. Returns one static page from any public Shopify storefront, by path handle and the required url of the store. The response has the page's title, URL, times and its content as plain text. Unknown handles return 404. Localhost, private-network and credentialed URLs are rejected.

Input Schema

NameRequiredDescriptionDefault
urlYesShopify storefront URL
handleYesPage handle

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/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 useful work: it discloses the return shape (title, URL, times, content as plain text), the 404 behavior for unknown handles, and the input-rejection policy for local/private/credentialed URLs. It omits rate limits and any auth/error detail beyond 404.

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?

Front-loaded with the core action, then return shape, then error/constraint notes; each sentence adds distinct information with no filler. Slightly dense but no wasted clauses.

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?

For a 2-parameter read tool with no output schema and no annotations, the description covers what it returns, the failure mode (404), and input restrictions, which is nearly everything an agent needs to invoke it correctly. Only rate-limit and pagination/auth context are absent, and neither seems applicable here.

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%, but the schema descriptions are terse ('Shopify storefront URL', 'Page handle'), so the description's clarification that handle is a path and url is the store URL adds modest value. It doesn't give format examples or state whether handle should include a leading slash.

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 ('Get Shopify page... Returns one static page') and distinguishes single-page retrieval from the sibling list tool shopify_pages by emphasizing 'one static page'. It stops short of explicitly naming shopify_pages as the alternative, so an agent must infer the split.

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 implied (fetch a single static page given a store URL and handle) and it discloses eligibility constraints (public storefronts only; localhost, private-network and credentialed URLs rejected). However it never names when to prefer shopify_pages or any sibling, nor any prerequisite beyond that constraint.

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