printify_get_productGet a single product's full details (variants, images, print areas, publish status). Printify REST: GET /v1/shops/{shop_id}/products/{product_id}.json.
| Name | Required | Description | Default |
|---|---|---|---|
| shop_id | Yes | Shop id — required. | |
| product_id | Yes | Product id — required. |
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 adds useful context beyond that by listing what the response includes (variants, images, print areas, publish status) and providing the REST endpoint. This gives the agent a clearer picture of the operation's behavior without contradicting the annotations.
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 two concise, front-loaded sentences. The first states the action and scope, the second provides the endpoint reference. Every sentence earns its place with no redundant information.
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 single-resource read tool with 2 required params, no output schema, and strong annotations, the description is complete. It states what the tool does, what details are returned, and the REST mapping. No critical gaps remain for agent decision-making.
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 100% with both params minimally described as required. The description does not add additional parameter meaning, but since the schema fully documents them, the baseline score of 3 is appropriate.
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 'Get a single product's full details' using a specific verb and resource, and enumerates the content (variants, images, print areas, publish status). This differentiates it from sibling tools like list_products and publish_product, making the purpose unambiguous.
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 use when needing full details for one product, contrasting with list tools that provide summaries. However, it does not explicitly name alternatives or state when not to use, so it lacks explicit exclusion guidance but offers clear contextual usage.
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.