Search manual and smart collections across Shopify stores using cursor pagination. Filter results with a query and control page size with first and after parameters to locate collections.
Search manual and smart collections with cursor pagination.
| Name | Required | Description | Default |
|---|---|---|---|
| after | No | ||
| first | No | ||
| query | 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 cover read-only, idempotent, non-destructive behavior, so the description does not need to restate that. It adds useful context by specifying 'manual and smart collections' and 'cursor pagination', which clarifies scope and pagination behavior beyond the schema.
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, front-loaded sentence with no filler or redundant information. Every word adds value: the resource type is explicit and the pagination behavior is stated concisely.
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 read-only, simple search tool, the description combined with annotations and schema provides a minimally viable picture. However, it lacks details such as query syntax, sorting behavior, and what the returned paginated response looks like, and there is no output schema to fill that gap.
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 must compensate, but it only alludes to pagination without explaining store, query, first, or after parameters. The phrase 'cursor pagination' gives some meaning to first/after, but it does not make the parameter semantics clear.
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 clear, specific verb-resource pair: 'Search manual and smart collections' with cursor pagination. It unambiguously differs from sibling tools like shopify_get_collection, which retrieves a single collection, and shopify_compare_collections, which compares collections.
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 the tool—when searching or listing collections—but does not explicitly state when not to use it or which sibling to prefer. No alternative tools are named, so the agent must infer usage context from the name and sibling list.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.