shopify_get_shopRetrieve Shopify store details including name, email, domain, plan, currency, timezone, and billing address to verify account settings and configuration.
Get store details: name, email, domain, Shopify plan, currency, timezone, billing address.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 destructiveHint=false, so safety is covered. The description adds genuine value by naming exactly which attributes the shop resource exposes, which no annotation or schema conveys (there is no output schema). It stops short of describing response shape, error cases, or rate-limit 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?
A single front-loaded sentence with a verb, resource and field list; there is no filler, hedging, or redundant restatement of the title.
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?
With zero parameters, full annotation coverage and no output schema, the field enumeration is effectively the only missing structured information, and the description supplies it. It is nearly complete, only lacking notes on error handling or whether a single shop object is always returned.
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?
The tool takes zero parameters, so there is nothing to document and the baseline of 4 applies. The description does not need to add parameter meaning.
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?
Specific verb ('Get') plus a specific resource ('store details') with an explicit enumeration of the returned fields (name, email, domain, plan, currency, timezone, billing address). This cleanly separates it from siblings like shopify_get_locations or shopify_get_products, which return other resource classes.
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 when to use it (when store-level details are needed) but never states it explicitly, names no alternatives, and gives no exclusions or prerequisites. For a zero-parameter getter with an obvious distinct scope, this is minimally viable rather than helpful.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.