Skip to main content
Glama

create_webhook

Set up automated event notifications from Klaviyo to your application by configuring webhook endpoints and subscribing to specific marketing events.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endpointYesURL endpoint for the webhook
eventsYesEvents to subscribe to
profile_idNoProfile ID for authentication

Implementation Reference

  • Executes the tool logic: constructs Klaviyo webhook payload with endpoint and events (optionally profile), posts to /webhooks/ via klaviyoClient, returns result or error.
    async (params) => {
      try {
        const payload = {
          data: {
            type: "webhook",
            attributes: {
              endpoint: params.endpoint,
              events: params.events
            }
          }
        };
        
        if (params.profile_id) {
          payload.data.relationships = {
            profile: {
              data: {
                type: "profile",
                id: params.profile_id
              }
            }
          };
        }
        
        const result = await klaviyoClient.post('/webhooks/', payload);
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error creating webhook: ${error.message}` }],
          isError: true
        };
      }
    },
  • Zod schema for tool inputs: required URL endpoint and events array, optional profile_id.
    {
      endpoint: z.string().url().describe("URL endpoint for the webhook"),
      events: z.array(z.string()).describe("Events to subscribe to"),
      profile_id: z.string().optional().describe("Profile ID for authentication")
    },
  • Registers the 'create_webhook' tool on the MCP server with name, input schema, handler function, and description.
    // Create webhook
    server.tool(
      "create_webhook",
      {
        endpoint: z.string().url().describe("URL endpoint for the webhook"),
        events: z.array(z.string()).describe("Events to subscribe to"),
        profile_id: z.string().optional().describe("Profile ID for authentication")
      },
      async (params) => {
        try {
          const payload = {
            data: {
              type: "webhook",
              attributes: {
                endpoint: params.endpoint,
                events: params.events
              }
            }
          };
          
          if (params.profile_id) {
            payload.data.relationships = {
              profile: {
                data: {
                  type: "profile",
                  id: params.profile_id
                }
              }
            };
          }
          
          const result = await klaviyoClient.post('/webhooks/', payload);
          return {
            content: [{ type: "text", text: JSON.stringify(result, null, 2) }]
          };
        } catch (error) {
          return {
            content: [{ type: "text", text: `Error creating webhook: ${error.message}` }],
            isError: true
          };
        }
      },
      { description: "Create a new webhook in Klaviyo" }
    );
  • src/server.js:43-43 (registration)
    Invokes registerWebhookTools which includes the registration of 'create_webhook'.
    registerWebhookTools(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