Skip to main content
Glama

create_event

Track customer interactions by creating events in Klaviyo with metric data, profile information, and custom properties for marketing automation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
metricYesMetric information for the event
profileYesProfile information for the event
propertiesNoAdditional properties for the event
timeNoISO timestamp for the event
valueNoNumeric value for the event

Implementation Reference

  • Executes the tool logic: formats event data into Klaviyo API payload and sends POST request via klaviyoClient.post.
    async (params) => {
      try {
        // Format payload according to the latest API structure
        const payload = {
          data: {
            type: "event",
            attributes: {
              metric: params.metric,
              profile: params.profile,
              properties: params.properties || {},
              time: params.time || new Date().toISOString(),
              value: params.value !== undefined ? params.value : 0
            }
          }
        };
        
        const result = await klaviyoClient.post('/events/', payload);
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error creating event: ${error.message}` }],
          isError: true
        };
      }
  • Zod schema validating input parameters for metric, profile, properties, time, and value.
    {
      metric: z.object({
        name: z.string().describe("Name of the metric")
      }).describe("Metric information for the event"),
      profile: z.object({
        email: z.string().email().describe("Email of the customer")
      }).describe("Profile information for the event"),
      properties: z.record(z.any()).optional().describe("Additional properties for the event"),
      time: z.string().optional().describe("ISO timestamp for the event"),
      value: z.number().optional().describe("Numeric value for the event")
    },
  • Registers the create_event tool on the MCP server with name, schema, handler function, and description.
    server.tool(
      "create_event",
      {
        metric: z.object({
          name: z.string().describe("Name of the metric")
        }).describe("Metric information for the event"),
        profile: z.object({
          email: z.string().email().describe("Email of the customer")
        }).describe("Profile information for the event"),
        properties: z.record(z.any()).optional().describe("Additional properties for the event"),
        time: z.string().optional().describe("ISO timestamp for the event"),
        value: z.number().optional().describe("Numeric value for the event")
      },
      async (params) => {
        try {
          // Format payload according to the latest API structure
          const payload = {
            data: {
              type: "event",
              attributes: {
                metric: params.metric,
                profile: params.profile,
                properties: params.properties || {},
                time: params.time || new Date().toISOString(),
                value: params.value !== undefined ? params.value : 0
              }
            }
          };
          
          const result = await klaviyoClient.post('/events/', payload);
          return {
            content: [{ type: "text", text: JSON.stringify(result, null, 2) }]
          };
        } catch (error) {
          return {
            content: [{ type: "text", text: `Error creating event: ${error.message}` }],
            isError: true
          };
        }
      },
      { description: "Create a new event in Klaviyo" }
  • src/server.js:35-35 (registration)
    Invokes registerEventTools to register the create_event tool (among others) on the main MCP server.
    registerEventTools(server);
  • Helper function post() used by the handler to make the API POST request with retry logic.
    export async function post(endpoint, data, fallbackFn) {
      return executeWithRetry(
        () => client.post(endpoint, data),
        'POST',
        endpoint,
        data,
        fallbackFn
      );
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