printify-mcp-server

printify_list_products

Retrieve a paginated list of products from a specified Printify shop. Use this to view product details and manage your catalog.

Instructions

Products in a shop, paginated.

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": {
      "shop_id": "<shop_id>"
    },
    "name": "printify_list_products"
  }
}

Input Schema

Name	Required	Description
`page`	No
`limit`	No
`shop_id`	Yes	Your shop id. printify_get_shops lists them.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 7, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations provided, the description must carry the behavioral disclosure burden. It adds only 'paginated'; it does not mention authentication, read-only status, response shape, error behavior, or pagination semantics. This is minimal disclosure for an unannotated tool.

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 extremely concise with no filler or repetition. The core facts—resource, scope, and pagination—are front-loaded in a single short phrase.

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

Completeness2/5

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

Given no annotations and no output schema, the description is too thin for an agent to confidently invoke the tool. Missing context includes what a product object looks like, how pagination works, how to obtain a shop_id, and which sibling tools are preferable in different situations.

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

Parameters2/5

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

Schema description coverage is only 33%, and the description does not compensate. The 'paginated' hint vaguely relates to page and limit, but the description explains none of the parameters beyond what the schema already names.

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

Purpose4/5

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

The description identifies the resource ('products') and scope ('in a shop') and hints at behavior ('paginated'). It distinguishes the tool from siblings like printify_get_product by plurality, though it lacks an explicit verb and doesn't name alternatives.

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

Usage Guidelines2/5

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

No guidance is given about when to use this tool versus siblings such as printify_get_product or printify_list_orders. The description states only what the tool returns, leaving usage decisions to inference.

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

Deploy Server