Skip to main content
Glama

create_coupon_code

Generate a unique coupon code for a specific Klaviyo coupon to enable personalized promotions and track marketing campaign effectiveness.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coupon_idYesID of the coupon
codeYesCoupon code

Implementation Reference

  • The main handler logic for create_coupon_code tool: builds Klaviyo API payload from params and performs POST to /coupon-codes/ endpoint.
    async (params) => {
      try {
        const payload = {
          data: {
            type: "coupon-code",
            attributes: {
              code: params.code
            },
            relationships: {
              coupon: {
                data: {
                  type: "coupon",
                  id: params.coupon_id
                }
              }
            }
          }
        };
        
        const result = await klaviyoClient.post('/coupon-codes/', payload);
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error creating coupon code: ${error.message}` }],
          isError: true
        };
      }
    },
  • Zod input schema defining required parameters: coupon_id (string) and code (string).
    {
      coupon_id: z.string().describe("ID of the coupon"),
      code: z.string().describe("Coupon code")
    },
  • Direct registration of the create_coupon_code tool via server.tool call within registerCouponTools.
    // Create coupon code
    server.tool(
      "create_coupon_code",
      {
        coupon_id: z.string().describe("ID of the coupon"),
        code: z.string().describe("Coupon code")
      },
      async (params) => {
        try {
          const payload = {
            data: {
              type: "coupon-code",
              attributes: {
                code: params.code
              },
              relationships: {
                coupon: {
                  data: {
                    type: "coupon",
                    id: params.coupon_id
                  }
                }
              }
            }
          };
          
          const result = await klaviyoClient.post('/coupon-codes/', payload);
          return {
            content: [{ type: "text", text: JSON.stringify(result, null, 2) }]
          };
        } catch (error) {
          return {
            content: [{ type: "text", text: `Error creating coupon code: ${error.message}` }],
            isError: true
          };
        }
      },
      { description: "Create a new coupon code in Klaviyo" }
    );
  • src/server.js:45-45 (registration)
    Top-level call to registerCouponTools(server), which registers the coupon tools including create_coupon_code.
    registerCouponTools(server);
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

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/ivan-rivera-projects/Klaviyo-MCP-Server-Enhanced'

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