Get normalized Shopify page details by providing a storefront URL and page handle. Returns cleaned page text from the credential-free JSON endpoint.
Get Shopify page. Returns normalized page detail from Shopify's credential-free /pages/{handle}.json endpoint. Page body HTML is returned as cleaned text only.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Shopify storefront URL | |
| handle | Yes | Page handle |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must carry full burden. It mentions credential-free access and that body HTML is returned as cleaned text, but lacks details on error handling, rate limits, or output structure beyond body text.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences are efficient and front-loaded with key info. First sentence could be redundant given the name, but overall no waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with no output schema or annotations, the description provides essential info but lacks details on what 'normalized page detail' includes. Slightly incomplete for an AI agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has 100% coverage with basic descriptions. The description adds context about the endpoint and cleaning, but does not enhance parameter understanding beyond what schema provides. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it gets a Shopify page, specifies the endpoint, and indicates return normalization. However, it does not explicitly distinguish from sibling tool 'shopify_pages' which likely lists pages, but the singular noun 'page' implies single retrieval.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like shopify_pages or shopify_product. No preconditions or exclusions are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.