Retrieve collection details, rules, and a paginated list of products from a specific store in the multi-store setup. Pass the store alias and collection ID to fetch the data.
Get collection details, rules and a page of products.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| after | No | ||
| first | No | ||
| store | Yes |
Changes observed during successful MCP inspections.
v1.6.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint false, so the safety profile is covered. The description adds useful behavioral context by clarifying that only 'a page of products' is returned, implying pagination rather than a full product listing.
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 concise sentence with no filler. It front-loads the action and immediately states the resource and return contents.
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?
The high-level return content is present and annotations cover safety, but with no output schema and no parameter descriptions in the schema or prose, the agent gets the minimum viable information. It is enough for a simple get-by-id call but not for confident parameter construction or sibling routing.
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%, so the description carries the compensation burden, but it only hints at 'collection' (id) and 'a page of products' (first/after). It does not explain the store parameter, the after cursor, or the first limit beyond what the schema itself already shows.
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 the specific verb 'Get' and resource 'collection', then enumerates the response scope: collection details, rules, and a page of products. This clearly separates it from shopify_get_product and from search/update/compare collection siblings.
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 purpose implies this is the tool to use when a caller needs a single collection's details, rules, or product page. However, it never names alternatives or says when not to use it, so routing among the many collection-related siblings is left to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.