Skip to main content
Glama

get_blueprint

Retrieve detailed product blueprint data from Printify's print-on-demand platform by specifying a blueprint ID. Enables AI assistants to integrate and manage product information effectively.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
blueprintIdYesBlueprint ID

Implementation Reference

  • Main handler function implementing the get_blueprint tool logic: fetches blueprint from Printify API, handles errors, formats MCP-compatible response.
    export async function getBlueprint(
      printifyClient: PrintifyAPI,
      blueprintId: 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 blueprint
        const blueprint = await printifyClient.getBlueprint(blueprintId);
        
        return {
          success: true,
          blueprint,
          response: {
            content: [{
              type: "text",
              text: `Blueprint details for ID ${blueprintId}:\n\n${JSON.stringify(blueprint, null, 2)}`
            }]
          }
        };
      } catch (error: any) {
        console.error('Error getting blueprint:', error);
        
        return {
          success: false,
          error,
          errorResponse: formatErrorResponse(
            error,
            'Get Blueprint',
            {
              BlueprintId: blueprintId
            },
            [
              'Check that the blueprint ID is valid',
              'Check that your Printify API key is valid',
              'Ensure your Printify account is properly connected'
            ]
          )
        };
      }
  • src/index.ts:459-489 (registration)
    MCP tool registration for 'get_blueprint': defines schema, thin wrapper handler that calls the service function.
    server.tool(
      "get_blueprint",
      {
        blueprintId: z.string().describe("Blueprint ID")
      },
      async ({ blueprintId }): Promise<{ content: any[], isError?: boolean }> => {
        // Import the printify blueprints service
        const { getBlueprint } = 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 getBlueprint(printifyClient, blueprintId);
    
        // 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 get_blueprint tool: requires blueprintId string.
    {
      blueprintId: z.string().describe("Blueprint ID")
    },
  • PrintifyAPI helper method that wraps the Printify SDK catalog.getBlueprint call.
    async getBlueprint(blueprintId: string) {
      try {
        // Use the catalog.getBlueprint method
        return await this.client.catalog.getBlueprint(blueprintId);
      } catch (error) {
        console.error(`Error fetching blueprint ${blueprintId}:`, 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