Resume an incomplete Shopify bulk export using its operation ID, and check its status to confirm whether the export remains partially incomplete.
Resume a bulk export by its operation ID. Partial exports remain explicitly incomplete.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| store | Yes |
Changes observed during successful MCP inspections.
v1.6.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds a small useful behavioral detail by saying 'Partial exports remain explicitly incomplete,' which warns the agent not to treat partial data as complete. However, the word 'Resume' sits awkwardly against the readOnlyHint and may mislead an agent into thinking the tool modifies export state.
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 short and front-loads the operation ID, which is good. However, the second sentence is cryptic and the first sentence's wording is imprecise, so the brevity does not translate into clear guidance.
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 no output schema, the description should explain what the agent will receive and how to use the result, but it does not. It also omits how the operation ID is obtained and what status values to expect, leaving the agent with too much uncertainty for a tool that is meant to report status.
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 0%, so the description must compensate for the schema's silence. It does clarify that the operation ID is the identifier used to locate the bulk export, but it completely fails to explain the 'store' parameter or how id and store relate.
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 says to 'Resume a bulk export by its operation ID,' which is ambiguous for a tool named 'status.' 'Resume' implies a state-changing or continuation action rather than a read-only status check, and it does not clearly distinguish this from the sibling shopify_bulk_export_start. The operation ID is mentioned, but the core purpose is obscured.
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?
No guidance is provided about when to use this tool versus alternatives such as shopify_bulk_export_start or when to poll status. It does not explain that this should be used after an export is started, nor does it describe the intended workflow.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.