Skip to main content
Glama

list_products

Retrieve a paginated list of products from Printify's print-on-demand platform. Specify page number and limit to filter results for efficient product management.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of products per page
pageNoPage number

Implementation Reference

  • The core handler function that implements the list_products tool logic: validates shop selection, fetches paginated products from Printify API, handles errors, and formats success/error responses.
    export async function listProducts(
      printifyClient: PrintifyAPI,
      options: {
        limit?: number;
        page?: number;
      } = {}
    ) {
      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.');
        }
    
        // Set default options
        const limit = options.limit || 10;
        const page = options.page || 1;
    
        // Get products
        const products = await printifyClient.getProducts(limit, page);
    
        return {
          success: true,
          products,
          response: formatSuccessResponse(
            'Products Retrieved Successfully',
            {
              Count: products.length,
              Page: page,
              Limit: limit,
              Shop: currentShop
            }
          )
        };
      } catch (error: any) {
        console.error('Error listing products:', error);
    
        return {
          success: false,
          error,
          errorResponse: formatErrorResponse(
            error,
            'List Products',
            {
              Shop: printifyClient.getCurrentShop(),
              Limit: options.limit,
              Page: options.page
            },
            [
              'Check that your Printify API key is valid',
              'Ensure your Printify account is properly connected',
              'Make sure you have selected a shop'
            ]
          )
        };
      }
    }
  • src/index.ts:184-215 (registration)
    MCP server registration of the 'list_products' tool, including input schema validation with Zod, dynamic import of the handler, client checks, and response formatting.
    server.tool(
      "list_products",
      {
        page: z.number().optional().default(1).describe("Page number"),
        limit: z.number().optional().default(10).describe("Number of products per page")
      },
      async ({ page, limit }): Promise<{ content: any[], isError?: boolean }> => {
        // Import the printify products service
        const { listProducts } = 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 listProducts(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 };
        }
      }
    );
  • Zod input schema for the list_products tool defining optional page and limit parameters with defaults and descriptions.
      page: z.number().optional().default(1).describe("Page number"),
      limit: z.number().optional().default(10).describe("Number of products per page")
    },
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