printful-mcp-server

createSyncProduct

Create a draft listing in your Printful store by adding a sync product with variants.

Instructions

Create a new sync product with variants. This creates a listing draft in your Printful store.

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": {
      "name": "<name>",
      "variants": "<variants>"
    },
    "name": "createSyncProduct"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Product name/title
`variants`	Yes	Array of variant objects
`thumbnail`	No	URL to thumbnail image
`external_id`	No	Your custom external ID for reference

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It adds useful context that this creates a 'listing draft' (not a live product) and is scoped to the Printful store. However, it does not disclose side effects, permissions, rate limits, or what happens on success or failure, leaving some behavioral uncertainty.

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?

The description is two short sentences, front-loaded with the action, and contains no filler or repetition. Every word contributes to the meaning.

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

Completeness3/5

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

For a creation tool with a complex nested variants structure, the schema provides excellent input coverage. However, there is no output schema and the description does not mention what the tool returns (e.g., the created product or ID), nor does it address any prerequisites beyond what the schema already notes. The description is adequate but lacks some completeness for a create operation.

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?

Schema description coverage is 100%, so all parameters (name, variants, thumbnail, external_id) and their nested properties are already fully described in the schema. The description adds no parameter-specific information beyond the redundant mention of 'with variants.'

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 clearly states the action ('Create a new sync product with variants') and the specific resource ('sync product' in the Printful store), and clarifies it creates a 'listing draft,' distinguishing it from get/update/delete sync product tools and mockup creation tools.

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

Usage Guidelines4/5

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

The description gives a clear usage context: use this tool when creating a new sync product. It does not explicitly mention alternatives or exclusions, but the verb 'create' and resource name make the intended use obvious among sibling tools.

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