Skip to main content
Glama

get_blueprints

Retrieve product blueprints from Printify's print-on-demand platform using pagination. Specify the page number and limit to fetch structured data for efficient product management and design integration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of blueprints per page
pageNoPage number

Implementation Reference

  • The main handler function that executes the 'get_blueprints' tool logic. It validates the client, fetches blueprints from Printify API, formats the response in MCP format, and handles errors.
    export async function getBlueprints(
      printifyClient: PrintifyAPI,
      options: {
        page?: number;
        limit?: number;
      } = {}
    ) {
      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.');
        }
        
        // Set default options
        const page = options.page || 1;
        const limit = options.limit || 10;
        
        // Get blueprints
        const blueprints = await printifyClient.getBlueprints();
        
        return {
          success: true,
          blueprints,
          response: {
            content: [{
              type: "text",
              text: `Available blueprints (page ${page}, limit ${limit}):\n\n${JSON.stringify(blueprints, null, 2)}`
            }]
          }
        };
      } catch (error: any) {
        console.error('Error getting blueprints:', error);
        
        return {
          success: false,
          error,
          errorResponse: formatErrorResponse(
            error,
            'Get Blueprints',
            {
              Page: options.page,
              Limit: options.limit
            },
            [
              'Check that your Printify API key is valid',
              'Ensure your Printify account is properly connected'
            ]
          )
        };
      }
    }
  • src/index.ts:425-456 (registration)
    Registers the 'get_blueprints' MCP tool on the server, defines the input schema using Zod (page and limit parameters), and provides the top-level handler that delegates to the service function.
    server.tool(
      "get_blueprints",
      {
        page: z.number().optional().default(1).describe("Page number"),
        limit: z.number().optional().default(10).describe("Number of blueprints per page")
      },
      async ({ page, limit }): Promise<{ content: any[], isError?: boolean }> => {
        // Import the printify blueprints service
        const { getBlueprints } = await import('./services/printify-blueprints.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 getBlueprints(printifyClient, { page, limit });
    
        // Return the result
        if (result.success) {
          return result.response as { content: any[], isError?: boolean };
        } else {
          return result.errorResponse as { content: any[], isError: boolean };
        }
      }
    );
  • Low-level helper method in PrintifyAPI class that calls the Printify SDK's catalog.listBlueprints() to fetch blueprints, used by the main handler.
    async getBlueprints() {
      try {
        // Use the catalog.listBlueprints method
        return await this.client.catalog.listBlueprints();
      } catch (error) {
        console.error('Error fetching blueprints:', error);
        throw error;
      }
    }
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