shopify_get_locationsRetrieve Shopify store locations with names, addresses, active status, and online-order fulfillment details to manage inventory and fulfillment settings.
All store locations: name, address, active status, and whether each fulfills online orders.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No |
Changes observed during successful MCP inspections.
v4.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior, so safety is covered. The description adds what data is returned (name, address, active status, fulfillment capability), but says nothing about pagination, rate limits, or the limit parameter's behavior.
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 a single, efficiently worded fragment that front-loads the resource. It wastes no words, though as a sentence fragment it leans terse rather than fully structured.
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 list operation with safety annotations already present, the description gives enough to understand the return shape. However, it omits any mention of the limit parameter or how results are constrained, leaving an agent to infer from the schema alone.
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 0% and the description does not mention the limit parameter at all. With a single input parameter that has a default, minimum, and maximum, the description should explain its role or at least acknowledge pagination, but it does neither.
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 names the resource (store locations) and enumerates key attributes returned, making the tool's output clear. It distinguishes from siblings like variant locations or inventory levels, though the verb 'get' is only in the tool name, not the description text.
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, when not to use it, or which alternatives exist. The description is a static field list with no contextual routing information.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.