printify_get_variantsList the variants (sizes, colors) a print provider offers for a blueprint. Printify REST: GET /v1/catalog/blueprints/{blueprint_id}/print_providers/{print_provider_id}/variants.json.
| Name | Required | Description | Default |
|---|---|---|---|
| blueprint_id | Yes | Blueprint id — required. | |
| print_provider_id | Yes | Print provider id — required. | |
| show_out_of_stock | No | Include out-of-stock variants (sent as show-out-of-stock=1). |
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?
Annotations already declare readOnlyHint=true, and the description's 'List' wording is consistent. The description adds the REST endpoint and clarifies the output as variant options (sizes, colors), but adds little beyond that. No contradictions.
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?
Two concise sentences, front-loaded with the primary purpose, followed by the technical endpoint reference. No unnecessary words or repetition.
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 read-only list operation with a fully documented schema and no required output schema, the description suffices. It states the resource, scope, and data type (variants with sizes/colors), making the tool usable without additional context.
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 input schema covers 100% of parameters with descriptions, so the baseline is 3. The tool description does not add any parameter-level details beyond what the schema already provides, nor does it explain show_out_of_stock behavior.
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 clearly states the tool lists variants (sizes, colors) for a blueprint from a print provider, using a specific verb and resource. It is distinct from sibling tools like printify_get_blueprint or printify_list_print_providers, which focus on other catalog aspects.
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 this tool (when you need variant data for a specific blueprint and provider) and provides the REST endpoint as a reference. However, it does not explicitly discuss alternatives or exclusions, such as when another catalog tool would be more appropriate.
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.