printify_list_shopsList all shops connected to the Printify account. This is the entry point — each shop's id is required by the product, order and webhook tools. Printify REST: GET /v1/shops.json.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already covers safety, and the description adds the REST endpoint and the fact that it returns all shops. It further explains the downstream dependency on shop IDs, providing useful behavioral context beyond the annotation.
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?
Three short sentences each serve a distinct purpose: stating what it does, why it matters, and how to call it. There is no wasted wording or redundancy.
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 zero-parameter, read-only list operation, the description fully covers purpose, usage, and integration point. No output schema is needed for such a simple operation, and the description does not leave significant gaps.
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 schema has zero parameters, so the description has nothing additional to explain beyond the trivially complete schema coverage. Baseline 4 is appropriate for a no-parameter tool.
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 uses a specific verb 'List' with the resource 'shops' and scope 'all connected to the Printify account', clearly distinguishing it from sibling list tools. It also explicitly identifies itself as the entry point, reinforcing its unique role.
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?
It states this is the entry point and that shop IDs are required by product, order, and webhook tools, implicitly directing the agent to call this first. There is no alternative listing tool, so the guidance is complete and actionable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Every tool targets a unique resource and action, with clear distinctions between 'get' and 'list' operations for related entities (blueprints, products, orders) and separate tools for shipping quotes, publishing, and webhooks. Descriptions further clarify any potential overlap, such as 'get_print_providers' versus 'list_print_providers'.
All tool names follow a consistent 'printify_<verb>_<noun>' pattern, using singular nouns for single-resource operations and plural for listing operations. This predictable structure makes it easy to guess tool names and understand their purpose.
With 14 tools, the set is well-scoped for the Printify domain, covering catalog data (blueprints, providers, variants), shop resources (products, orders, uploads, webhooks), and key actions (shipping quotes, publishing). The count is within the ideal range and each tool serves a distinct function.
The server provides comprehensive read operations for all major resources and includes publishing, but it lacks create/update/delete tools for products, orders, uploads, and webhooks. This limits the agent to monitoring and publishing workflows rather than full lifecycle management, leaving notable gaps for a complete Printify integration.