Skip to main content
Glama

get_product

Retrieve detailed product information from Printify's print-on-demand platform by providing the product ID, enabling efficient product management and integration with AI workflows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
productIdYesProduct ID

Implementation Reference

  • Core handler function that executes the get_product tool logic: validates selected shop, fetches product details from Printify API client, formats success or error response.
    export async function getProduct(
      printifyClient: PrintifyAPI,
      productId: string
    ) {
      try {
        // Validate shop is selected
        const currentShop = printifyClient.getCurrentShop();
        if (!currentShop) {
          throw new Error('No shop is currently selected. Use the list-shops and switch-shop tools to select a shop.');
        }
    
        // Get product
        const product = await printifyClient.getProduct(productId);
    
        return {
          success: true,
          product,
          response: formatSuccessResponse(
            'Product Retrieved Successfully',
            {
              ProductId: productId,
              Title: product.title,
              Shop: currentShop
            }
          )
        };
      } catch (error: any) {
        console.error('Error getting product:', error);
    
        return {
          success: false,
          error,
          errorResponse: formatErrorResponse(
            error,
            'Get Product',
            {
              ProductId: productId,
              Shop: printifyClient.getCurrentShop()
            },
            [
              'Check that the product ID is valid',
              'Ensure your Printify account is properly connected',
              'Make sure you have selected a shop'
            ]
          )
        };
      }
  • src/index.ts:218-248 (registration)
    Registers the 'get_product' MCP tool, defines input schema (productId: string), provides wrapper handler that initializes service and delegates to core handler.
    server.tool(
      "get_product",
      {
        productId: z.string().describe("Product ID")
      },
      async ({ productId }): Promise<{ content: any[], isError?: boolean }> => {
        // Import the printify products service
        const { getProduct } = await import('./services/printify-products.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 getProduct(printifyClient, productId);
    
        // 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 get_product tool requiring productId as string.
    {
      productId: z.string().describe("Product ID")
    },
  • Low-level helper method in PrintifyAPI client that calls Printify SDK to retrieve product by ID.
    async getProduct(productId: string) {
      if (!this.shopId) {
        throw new Error('Shop ID is not set. Call setShopId() first.');
      }
    
      try {
        // Use the products.getOne method with the product ID
        return await this.client.products.getOne(productId);
      } catch (error) {
        console.error(`Error fetching product ${productId}:`, 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