Retrieve orders from your Printify shop, sorted newest first. Filter by status and paginate results to review and manage order workflows.
Orders in a shop, most recent first.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| limit | No | ||
| status | No | Filter by Printify order status. | |
| shop_id | Yes | Your shop id. printify_get_shops lists them. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, so the description must carry the burden of behavioral disclosure. It does disclose one meaningful behavior: results are ordered 'most recent first'. However, it does not mention pagination behavior, return shape, or any caveats beyond the ordering trait, leaving gaps in transparency.
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 very short and front-loads the resource and ordering, with no filler or redundant statements. It is efficient, but it is telegraphic and could benefit from a verb or slightly more context without becoming verbose.
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?
With four parameters, no annotations, and no output schema, the description is too sparse to be fully contextual. It only states the resource and sort order, omitting pagination semantics, status filtering intent, output expectations, and how this tool relates to sibling order/list tools.
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 description adds no parameter-level meaning; it does not explain page, limit, status, or shop_id beyond what the schema already says. Since schema description coverage is only 50%, the description needed to compensate for the undocumented page and limit parameters but does not.
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 identifies the resource ('orders'), scopes it to 'a shop', and specifies the ordering ('most recent first'), which makes the core operation clear. It lacks an explicit verb like 'list' or 'retrieve', but the tool name and phrasing imply listing. It is distinguishable from sibling list tools by naming the 'orders' resource.
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 gives no guidance on when to use this tool versus alternatives such as printify_list_products or printify_list_operations. It does not mention whether this is the default order lookup or when filtering by status would be appropriate. Usage context is only weakly implied by 'Orders in a shop'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.