Skip to main content
Glama
plutzilla

Omnisend MCP Server

createProduct

Add products to your Omnisend catalog with details like title, description, variants, images, and price for marketing automation.

Instructions

Create a new product in the Omnisend catalog. Product data can include details like title, description, variants, images, price, and more.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the 'createProduct' MCP tool. Calls the API createProduct, filters response with filterProductFields, returns formatted JSON text content, handles errors.
    async (args) => {
      try {
        const response = await createProduct(args.productData);
        
        // Filter product data to include only defined fields
        const filteredProduct = filterProductFields(response);
        
        return {
          content: [
            { 
              type: "text", 
              text: JSON.stringify(filteredProduct, null, 2) 
            }
          ]
        };
      } catch (error) {
        if (error instanceof Error) {
          return { content: [{ type: "text", text: `Error: ${error.message}` }] };
        }
        return { content: [{ type: "text", text: "An unknown error occurred" }] };
      }
    }
  • JSON Schema defining input for 'createProduct' tool: requires 'productData' as flexible object.
    {
      additionalProperties: false,
      properties: {
        productData: { 
          additionalProperties: true,
          description: "Product data", 
          properties: {},
          type: "object"
        }
      },
      required: ["productData"],
      type: "object"
    },
  • Registration of 'createProduct' tool via server.tool(), specifying name and description.
    server.tool(
      "createProduct",
      "Create a new product in the Omnisend catalog. Product data can include details like title, description, variants, images, price, and more.",
  • API helper implementing the product creation by POSTing to Omnisend '/products' endpoint.
    export const createProduct = async (productData: Partial<Product>): Promise<Product> => {
      try {
        const response = await omnisendApi.post<Product>('/products', productData);
        return response.data;
      } catch (error) {
        if (error instanceof Error) {
          throw new Error(`Error creating product: ${error.message}`);
        } else {
          throw new Error('Unknown error occurred when creating product');
        }
      }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a creation operation but doesn't mention whether it requires authentication, what happens on duplicate products, rate limits, or what the response looks like. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is perfectly concise - two sentences that immediately state the purpose and provide useful context about data content. Every word earns its place with no redundancy or unnecessary elaboration, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a creation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what happens after creation (e.g., returns product ID, success status), error handling, authentication requirements, or how it differs from similar operations like 'replaceProduct'. Given the complexity of product creation and lack of structured metadata, more context is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so the baseline is 4. The description adds value by specifying what product data 'can include' (title, description, variants, images, price, and more), giving semantic context about expected content even though no formal parameters are defined in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Create a new product') and resource ('in the Omnisend catalog'), making the purpose immediately understandable. It distinguishes from siblings like 'deleteProduct' and 'updateCategory' by specifying creation rather than modification or deletion. However, it doesn't explicitly differentiate from 'replaceProduct' which might also involve product creation in some contexts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'replaceProduct' or 'updateProduct' (which doesn't exist but 'updateCategory' suggests similar patterns). It mentions what data can be included but gives no context about prerequisites, error conditions, or typical use cases compared to sibling tools.

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

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/plutzilla/omnisend-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server