Skip to main content
Glama

publish_product

Automate publishing of Printify product details including title, description, images, variants, and tags by specifying product ID and publish settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
productIdYesProduct ID
publishDetailsNoPublish details

Implementation Reference

  • Core handler function for the publish_product MCP tool. Validates the current shop selection, calls the Printify API client's publishProduct method, handles errors, and formats structured success/error responses.
    export async function publishProduct(
      printifyClient: PrintifyAPI,
      productId: string,
      publishDetails?: {
        title?: boolean;
        description?: boolean;
        images?: boolean;
        variants?: boolean;
        tags?: boolean;
      }
    ) {
      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.');
        }
    
        // Publish product
        const result = await printifyClient.publishProduct(productId, publishDetails);
    
        return {
          success: true,
          result,
          response: formatSuccessResponse(
            'Product Published Successfully',
            {
              ProductId: productId,
              Shop: currentShop
            }
          )
        };
      } catch (error: any) {
        console.error('Error publishing product:', error);
    
        return {
          success: false,
          error,
          errorResponse: formatErrorResponse(
            error,
            'Publish Product',
            {
              ProductId: productId,
              PublishDetails: publishDetails,
              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:385-422 (registration)
    MCP server.tool registration for 'publish_product' tool, including Zod input schema validation and thin wrapper handler that injects the global printifyClient and delegates to the core handler.
    server.tool(
      "publish_product",
      {
        productId: z.string().describe("Product ID"),
        publishDetails: z.object({
          title: z.boolean().optional().default(true).describe("Publish title"),
          description: z.boolean().optional().default(true).describe("Publish description"),
          images: z.boolean().optional().default(true).describe("Publish images"),
          variants: z.boolean().optional().default(true).describe("Publish variants"),
          tags: z.boolean().optional().default(true).describe("Publish tags")
        }).optional().describe("Publish details")
      },
      async ({ productId, publishDetails }): Promise<{ content: any[], isError?: boolean }> => {
        // Import the printify products service
        const { publishProduct } = 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 publishProduct(printifyClient, productId, publishDetails);
    
        // Return the result
        if (result.success) {
          return result.response as { content: any[], isError?: boolean };
        } else {
          return result.errorResponse as { content: any[], isError: boolean };
        }
      }
    );
  • Zod schema for input parameters of the publish_product tool: productId (string) and optional publishDetails object specifying which product fields to publish.
    {
      productId: z.string().describe("Product ID"),
      publishDetails: z.object({
        title: z.boolean().optional().default(true).describe("Publish title"),
        description: z.boolean().optional().default(true).describe("Publish description"),
        images: z.boolean().optional().default(true).describe("Publish images"),
        variants: z.boolean().optional().default(true).describe("Publish variants"),
        tags: z.boolean().optional().default(true).describe("Publish tags")
      }).optional().describe("Publish details")
    },
  • PrintifyAPI class method that wraps the Printify SDK's products.publishOne call, with shop ID validation and enhanced error handling.
    async publishProduct(productId: string, publishData: any) {
      if (!this.shopId) {
        throw new Error('Shop ID is not set. Call setShopId() first.');
      }
    
      try {
        // Use the products.publishOne method with the product ID and publish data
        return await this.client.products.publishOne(productId, publishData);
      } catch (error) {
        console.error(`Error publishing product ${productId}:`, error);
        throw this.enhanceError(error, publishData);
      }
    }
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