printful-mcp-server

changeStore

Switch to a different Printful store using its store ID, enabling account holders to manage multiple stores.

Instructions

Switch to a different store (for accounts with multiple stores)

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": {
      "store_id": "<store_id>"
    },
    "name": "changeStore"
  }
}

Input Schema

Name	Required	Description	Default
`store_id`	Yes	The store ID to switch to

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action 'Switch to a different store' without explaining side effects (e.g., whether it changes session state, if it is reversible, or what happens on invalid store_id). This is a significant gap for a state-changing 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 a single, front-loaded sentence that directly states the tool's purpose and a key caveat. There is no wasted words or redundant information.

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?

For a simple tool it has a clear purpose, but it lacks important context such as what 'switching' entails (e.g., does it affect the current session?), what the expected return value is (no output schema), and how to obtain a valid store_id. The description is sparse and does not fully enable correct invocation without additional assumptions.

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% for the single parameter store_id, which has a clear description. The tool description adds no additional parameter semantics beyond the schema, so the baseline of 3 applies.

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 'Switch to a different store' clearly states the action and resource, and the parenthetical '(for accounts with multiple stores)' adds context. It distinguishes from sibling read-only tools like getStore and getStores, though it does not explicitly state that it changes the active store context for subsequent API calls.

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 provides a clear usage context: 'for accounts with multiple stores.' It implies when to use it, but does not mention alternatives or explicitly state when not to use it (e.g., accounts with a single store). This meets the 'clear context, no exclusions' level.

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