printify_get_orderGet a single order's full details, including shipments (carrier + tracking numbers). Printify REST: GET /v1/shops/{shop_id}/orders/{order_id}.json.
| Name | Required | Description | Default |
|---|---|---|---|
| shop_id | Yes | Shop id — required. | |
| order_id | Yes | Order 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 declare readOnlyHint=true, and the description adds value by specifying it returns full details including shipments and the REST endpoint. This provides useful behavioral context beyond the schema, though it doesn't mention response format edge cases or error behavior.
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 sentences, front-loaded with the core purpose and valuable detail (shipments). No wasted words; the endpoint reference is compact and informative.
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 get-by-id operation with readOnlyHint and complete schema coverage, the description adequately explains what the tool returns (full details, shipments) and the endpoint. No output schema exists, but the description covers the key return information an agent needs.
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 coverage is 100% for the two parameters, but the description adds the REST endpoint path showing how shop_id and order_id map to URL placeholders. This reinforces parameter roles beyond the schema's minimal 'required' notes.
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 specific verb ('Get') and resource ('a single order's full details'), clearly distinguishing it from the sibling list tool. It also highlights key included data (shipments with carrier and tracking numbers), making the purpose unmistakable.
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 a single order's details are needed, contrasting with the sibling list_orders tool. It does not explicitly state when not to use it or name alternatives, but the single-vs-list distinction is clear enough for basic selection.
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.