Skip to main content
Glama

switch_shop

Switch active shops within the Printify MCP Server by providing the target shop ID, enabling seamless management of print-on-demand operations across multiple accounts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
shopIdYesThe ID of the shop to switch to

Implementation Reference

  • The core handler function `switchPrintifyShop` that performs shop validation, switches the current shop using the Printify client, and formats the response.
    export async function switchPrintifyShop(printifyClient: PrintifyAPI, shopId: string) {
      try {
        // Validate client is initialized
        if (!printifyClient) {
          throw new Error('Printify API client is not initialized. The PRINTIFY_API_KEY environment variable may not be set.');
        }
        
        // Get shops and find the requested shop
        const shops = await printifyClient.getShops();
        const shop = shops.find((s: any) => s.id.toString() === shopId);
        
        if (!shop) {
          throw new Error(`Shop with ID ${shopId} not found. Use the list-shops tool to see available shops.`);
        }
        
        // Switch to the requested shop
        printifyClient.setShopId(shopId);
        
        return {
          success: true,
          shop,
          response: {
            content: [{
              type: "text",
              text: `Switched to shop: ${shop.title} (ID: ${shop.id}, Channel: ${shop.sales_channel})`
            }]
          }
        };
      } catch (error: any) {
        console.error('Error switching Printify shop:', error);
        
        return {
          success: false,
          error,
          errorResponse: formatErrorResponse(
            error,
            'Switch Printify Shop',
            {
              ShopId: shopId
            },
            [
              'Check that the shop ID is valid',
              'Use the list-shops tool to see available shops',
              'Ensure your Printify account is properly connected'
            ]
          )
        };
      }
    }
  • src/index.ts:149-179 (registration)
    MCP server registration of the 'switch_shop' tool, defining the input schema (shopId: string) and wrapper that imports and calls the handler function.
    server.tool(
      "switch_shop",
      {
        shopId: z.string().describe("The ID of the shop to switch to")
      },
      async ({ shopId }): Promise<{ content: any[], isError?: boolean }> => {
        // Import the printify shops service
        const { switchPrintifyShop } = await import('./services/printify-shops.js');
    
        // Check if client is initialized
        if (!printifyClient) {
          return {
            content: [{
              type: "text",
              text: "Printify API client is not initialized. The PRINTIFY_API_KEY environment variable may not be set."
            }],
            isError: true
          };
        }
    
        // Call the service
        const result = await switchPrintifyShop(printifyClient, shopId);
    
        // Return the result
        if (result.success) {
          return result.response as { content: any[], isError?: boolean };
        } else {
          return result.errorResponse as { content: any[], isError: boolean };
        }
      }
    );
  • Zod input schema for the switch_shop tool, requiring a shopId string.
      shopId: z.string().describe("The ID of the shop to switch to")
    },
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TSavo/printify-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server