Skip to main content
Glama

get_printify_status

Retrieve the current operational status of Printify services. Monitor service health, check for outages or maintenance, and ensure your print-on-demand workflow runs smoothly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:87-115 (registration)
    Registration of the 'get_printify_status' tool via server.tool() with empty schema {}, handler imports getPrintifyStatus from printify-shops service and calls it with the printifyClient.
    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 };
        }
      }
    );
  • The actual handler function getPrintifyStatus that calls PrintifyAPI.getShops() and getCurrentShop(), returning a formatted status response with shop count and current shop info.
    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'
            ]
          )
        };
      }
    }
  • Imports PrintifyAPI type and formatErrorResponse/formatSuccessResponse helpers used by the handler.
    import { PrintifyAPI } from '../printify-api.js';
    import { formatErrorResponse, formatSuccessResponse } from '../utils/error-handler.js';
  • formatErrorResponse utility used by getPrintifyStatus when an error occurs.
    export function formatErrorResponse(
      error: any,
      step: string,
      context: Record<string, any> = {},
      tips: string[] = []
    ) {
      // Get error details
      const errorType = error.constructor.name;
      const errorMessage = error.message || 'Unknown error';
      const errorStack = error.stack ? error.stack.split('\n').slice(0, 3).join('\n') : 'Not available';
      
      // Format the error message
      let text = `āŒ **Error in ${step}**\n\n`;
      
      // Add context information
      Object.entries(context).forEach(([key, value]) => {
        if (typeof value === 'string' && value.includes('"')) {
          text += `- **${key}**: ${value}\n`;
        } else if (typeof value === 'object') {
          text += `- **${key}**: ${JSON.stringify(value)}\n`;
        } else {
          text += `- **${key}**: "${value}"\n`;
        }
      });
      
      text += `- **Error**: ${errorMessage}\n\n`;
      
      // Add detailed diagnostic information
      text += `=== DETAILED DIAGNOSTIC INFORMATION ===\n\n`;
      text += `- **Error Type**: ${errorType}\n`;
      text += `- **Error Stack**: ${errorStack}\n`;
      
      // Add additional context details
      Object.entries(context).forEach(([key, value]) => {
        if (key !== 'Prompt' && key !== 'Model' && key !== 'Error') {
          if (typeof value === 'object' && value !== null) {
            text += `- **${key}**: ${JSON.stringify(value, null, 2)}\n`;
          } else if (value !== undefined && value !== null) {
            text += `- **${key}**: ${value}\n`;
          }
        }
      });
      
      // Add system information
      text += `- **Current Working Directory**: ${process.cwd()}\n`;
      text += `- **Node.js Version**: ${process.version}\n`;
      text += `- **Platform**: ${process.platform}\n\n`;
      
      // Add API response data if available
      if (error.response) {
        text += `- **API Response Status**: ${error.response.status}\n`;
        text += `- **API Response Data**: ${JSON.stringify(error.response.data, null, 2)}\n\n`;
      }
      
      // Add tips if provided
      if (tips.length > 0) {
        text += `\nšŸ”„ Please try again with a different prompt or parameters.\n\n`;
        text += 'šŸ’” **Tips**:\n';
        tips.forEach(tip => {
          text += `• ${tip}\n`;
        });
      }
      
      return {
        content: [{ type: "text", text }],
        isError: true
      };
    }
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

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