Skip to main content
Glama

Printify MCP by usefulapi

by io.usefulapi
OverviewDiscussionsAdmin

Copy products between shops

printify_copy_products
DestructiveIdempotent

Preview or copy selected products or a complete catalog between two Printify shops in the same account. Preserves title, description, blueprint/provider, variant IDs/prices/enabled flags, artwork IDs and print-area transforms. Preserves canvas side printing and image pattern rotation. This initial workflow does not copy tags, SKUs, channel IDs, publication state or generated mockups. Products with text/personalization layers are explicitly refused because their creation fields are read-only. Preview by default. confirm:true starts/resumes a durable bounded job; save job_id and keep calling with that job_id and confirm:true until complete. Duplicate prevention remembers copies made by this connector, including across restarts/jobs; pre-existing copies made elsewhere are not detected. An uncertain create is never automatically retried: inspect the target and use printify_resolve_copy. Do not change the source catalog during an all-products run. Requires shops.read/products.read/products.write. Confirmed copying requires the hosted connector's durable coordinator.

Input Schema

NameRequiredDescriptionDefault
job_idNoA previously returned job_id to resume; supply the same source and target shops.
confirmNoFalse/omitted previews only. True authorizes creation of new draft products.
batch_sizeNoMaximum creates in this call (default 1). Calls are also bounded when skipping prior copies.
product_idsNoSelected source product IDs; mutually exclusive with all_products:true. Omit when resuming job_id.
all_productsNoCopy all source products with resumable pagination. Omit when resuming job_id.
start_new_jobNoWith confirm:true and a selection, restart enumeration after source-catalog changes; never combine with job_id. Permanent copied and uncertain mappings are retained.
source_shop_idYesSource shop ID; the token must have access to both shops in the same Printify account.
target_shop_idYesDifferent target shop ID. New products stay as drafts and are not published.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond idempotentHint/destructiveHint by enumerating exactly what is preserved, what is not copied (tags, SKUs, channel IDs, publication state, mockups), which products are refused and why, the durable bounded-job loop, and the bounded reach of duplicate detection. It also states created items stay drafts and are never auto-retried, which directly informs the destructive/idempotent hints.

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

Conciseness4/5

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

Front-loaded with what it does and what it preserves, then behavior, then job mechanics, then permissions – a sensible ordering for a complex tool. It is dense but nearly every sentence carries a constraint an agent needs; a few clauses could be tightened.

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

Completeness5/5

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

An 8-parameter, stateful, multi-call workflow tool with no output schema and heavy preconditions – the description supplies job resumption instructions, permission requirements, and the hosted-coordinator prerequisite. Nothing essential to correct invocation is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds cross-parameter semantics the schema states only in isolation: job_id must be reused with the same source/target shops, and job_id must never be combined with start_new_job. Minor redundancy with the schema's own confirm/batch_size explanations keeps it from a 5.

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?

States a specific verb and resource ('Preview or copy selected products or a complete catalog between two Printify shops') plus the scope constraint (same account). An agent can immediately tell this apart from read-only siblings like printify_get_product or printify_list_products.

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

Usage Guidelines5/5

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

Explicit when-to-use rules: preview is the default, confirm:true authorizes creation, start_new_job applies only after source-catalog changes, do-not-change-source during all-products runs, and route uncertain creates to printify_resolve_copy. Withholding conditions are spelled out, not left to inference.

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

All Printify MCP by usefulapi toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources