Skip to main content
Glama

get_printify_status

Retrieve real-time status updates from Printify's print-on-demand platform using the MCP server, enabling seamless integration with AI assistants for product creation and design management.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler logic for get_printify_status: the getPrintifyStatus function that validates the client, fetches shops and current shop, and formats the status response.
    export async function getPrintifyStatus(printifyClient: PrintifyAPI) {
      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 current shop
        const shops = await printifyClient.getShops();
        const currentShop = printifyClient.getCurrentShop();
        
        return {
          success: true,
          shops,
          currentShop,
          response: {
            content: [{
              type: "text",
              text: `Printify API Status:\n\n` +
                    `Connected: Yes\n` +
                    `Available Shops: ${shops.length}\n` +
                    `Current Shop: ${currentShop ? `${currentShop.title} (ID: ${currentShop.id})` : 'None'}`
            }]
          }
        };
      } catch (error: any) {
        console.error('Error getting Printify status:', error);
        
        return {
          success: false,
          error,
          errorResponse: formatErrorResponse(
            error,
            'Get Printify Status',
            {},
            [
              'Check that your Printify API key is valid',
              'Ensure your Printify account is properly connected'
            ]
          )
        };
      }
    }
  • src/index.ts:87-115 (registration)
    Registration of the 'get_printify_status' tool via server.tool(). The inline handler checks client initialization and delegates to the getPrintifyStatus service function, returning formatted response.
    server.tool(
      "get_printify_status",
      {},
      async ({}): Promise<{ content: any[], isError?: boolean }> => {
        // Import the printify shops service
        const { getPrintifyStatus } = 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 getPrintifyStatus(printifyClient);
    
        // Return the result
        if (result.success) {
          return result.response as { content: any[], isError?: boolean };
        } else {
          return result.errorResponse as { content: any[], isError: boolean };
        }
      }
    );
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