printful-mcp-server

getSyncProduct

Retrieve a specific synchronized product and all its variants from Printful, providing complete product details in one lookup.

Instructions

Get a single sync product with all its variants

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": {
      "sync_product_id": "<sync_product_id>"
    },
    "name": "getSyncProduct"
  }
}

Input Schema

Name	Required	Description	Default
`sync_product_id`	Yes	Sync product ID (or @external_id)

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?

No annotations are provided, so the description carries the full burden. The verb 'Get' implies a read-only operation, and 'with all its variants' gives some behavioral context, but it does not disclose error behavior, permissions, or return format details beyond that. It is adequate but not rich.

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 a single, clear sentence that states the essential purpose without unnecessary words. Every word adds value, making it highly concise and well-structured.

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 retrieval tool, the description covers the core purpose and return scope ('all its variants'). It does not detail the output structure, but no output schema exists, and the tool's simplicity makes this acceptable. Slight gap: no mention of what happens if not found, but overall complete enough.

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%, and the parameter 'sync_product_id' is already well described in the schema, including the '@external_id' option. The description adds no additional parameter meaning beyond what the schema provides, so the baseline of 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 the specific verb 'Get' with a clear resource ('sync product') and scope ('single' with 'all its variants'). It distinguishes itself from the plural sibling getSyncProducts and the more generic getProduct by specifying 'sync product' and 'single'.

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 for retrieving one sync product with variants, but it does not explicitly state when to choose this tool over siblings like getSyncProducts or getProduct. No exclusions or alternative guidance is provided, so it relies on the implied context.

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