Skip to main content
Glama

delete_product

Remove a product from Printify's print-on-demand platform by specifying its unique product ID, ensuring accurate product management and inventory control.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
productIdYesProduct ID

Implementation Reference

  • src/index.ts:352-382 (registration)
    MCP tool registration for 'delete_product'. Defines the tool name, input schema (productId: string), and a thin async handler that checks client initialization, imports and calls the service layer deleteProduct function, and returns formatted response.
    server.tool(
      "delete_product",
      {
        productId: z.string().describe("Product ID")
      },
      async ({ productId }): Promise<{ content: any[], isError?: boolean }> => {
        // Import the printify products service
        const { deleteProduct } = 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 deleteProduct(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 };
        }
      }
    );
  • Primary handler function for deleting a product. Validates that a shop is selected, calls the Printify API client's deleteProduct method, and returns success or formatted error response using error-handler utilities.
    export async function deleteProduct(
      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.');
        }
    
        // Delete product
        await printifyClient.deleteProduct(productId);
    
        return {
          success: true,
          response: formatSuccessResponse(
            'Product Deleted Successfully',
            {
              ProductId: productId,
              Shop: currentShop
            }
          )
        };
      } catch (error: any) {
        console.error('Error deleting product:', error);
    
        return {
          success: false,
          error,
          errorResponse: formatErrorResponse(
            error,
            'Delete 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'
            ]
          )
        };
      }
    }
  • Zod input schema for the delete_product tool: requires a single string parameter 'productId'.
    {
      productId: z.string().describe("Product ID")
    },
  • Low-level PrintifyAPI client method that performs the actual deletion by calling this.client.products.deleteOne(productId), which interacts with the Printify SDK.
    async deleteProduct(productId: string) {
      if (!this.shopId) {
        throw new Error('Shop ID is not set. Call setShopId() first.');
      }
    
      try {
        // Use the products.deleteOne method with the product ID
        return await this.client.products.deleteOne(productId);
      } catch (error) {
        console.error(`Error deleting 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