List public retail locations for a Shop.app merchant profile by handle; returns up to 50 locations.
List Shop.app shop locations. Returns public retail locations for a Shop.app merchant profile.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum locations, defaults to 10 and supports up to 50 | |
| handle | Yes | Shop handle |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must cover behavioral aspects but only states it returns public retail locations. It omits details like authentication needs, read-only nature, rate limits, or response structure, leaving gaps for an agent.
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?
The description is extremely concise with two clear sentences. Every word serves a purpose, and no unnecessary information is included.
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?
Given the simplicity (2 parameters, no output schema), the description is adequate but minimal. It could be improved by hinting at output details or common usage patterns, but it is not incomplete for a basic list tool.
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 coverage is 100%, so baseline is 3. The description adds no extra meaning beyond the schema; it simply restates the parameters. No additional context or clarifications are provided.
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 the tool lists Shop.app shop locations for a merchant profile. It uses a specific verb and resource, and the name distinguishes it from siblings like shop_app_shop and shop_app_shop_products.
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?
The description implies usage for retrieving locations but provides no explicit guidance on when to use it versus alternatives or when not to use it. Context suggests it's the correct tool for locations, but no exclusions are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.