Resolve a public Shopify storefront URL and return its metadata as clean JSON for store research and commerce analysis.
Get Shopify store metadata. Resolves a public Shopify storefront and returns its metadata.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Shopify storefront URL |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations and no output schema, the description carries the full behavioral burden. It hints that the storefront must be public (implying no auth-gated access) but discloses nothing about rate limits, error behavior for invalid URLs, or what the metadata payload contains.
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?
Two short sentences, front-loaded with the core action. Slight redundancy between the two sentences (both mention metadata), but overall tight and efficient.
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 one-parameter lookup this is minimally adequate. However, without an output schema the description could specify what metadata fields are returned, leaving a gap for an agent expecting to know the response shape.
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 description coverage is 100% for the single `url` parameter, so the schema already documents it. The description adds a marginal hint that the URL must point to a public Shopify storefront, but no syntax or format detail beyond the schema.
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 states a specific verb+resource ("Get Shopify store metadata") and clarifies it resolves a public storefront. It is reasonably distinct from siblings like shopify_product or shopify_collections, though the term "metadata" remains somewhat vague about what exactly is returned.
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 when-to-use guidance is provided. There is no mention of when to call this versus the many sibling store-related tools (shopify_products, shopify_sitemaps, etc.), nor any prerequisites for the URL. Usage is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.