printful-mcp-server

getMockupTask

Check the status of a mockup generation task and retrieve result URLs using its task key.

Instructions

Check status of a mockup generation task and get result URLs

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "task_key": "<task_key>"
    },
    "name": "getMockupTask"
  }
}

Input Schema

Name	Required	Description	Default
`task_key`	Yes	Task key from createMockupTask

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A3.8/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description conveys that this is a read operation (check/get) but does not explicitly state that it has no side effects, or disclose behavior such as possible statuses, error handling, or rate limits. With no annotations provided, the description carries the full burden but offers only basic behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One concise sentence of 10 words, perfectly front-loaded with the action and resource, no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-parameter tool with no output schema or annotations, the description adequately covers the purpose and expected result (status and URLs). It could benefit from mentioning what happens during task processing, but overall it is sufficiently complete for its complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already provides a complete description of the single parameter (task_key, 'Task key from createMockupTask') at 100% coverage. The description adds no additional meaning about the parameter format or semantics, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses specific verbs ('Check', 'get') and a clear resource ('mockup generation task'), and explicitly states the outcome (result URLs). This clearly distinguishes it from siblings like createMockupTask (creation) and getMockupTemplates (template listing).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage after task creation via the phrase 'check status', but does not explicitly state when to use it versus alternatives, nor mention exclusions. The schema's parameter description hints at 'from createMockupTask', but that is not in the tool description itself.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.