Skip to main content
Glama

request_profile_deletion

Remove customer profiles from Klaviyo by providing email, phone number, or profile ID to comply with data privacy regulations and manage marketing lists.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNoEmail of the profile to delete
phone_numberNoPhone number of the profile to delete
profile_idNoID of the profile to delete

Implementation Reference

  • Handler function that processes the deletion request by building a payload from input params and posting to Klaviyo's data-privacy-deletion-jobs endpoint, returning the result or error.
    async (params) => {
      try {
        const payload = {
          data: {
            type: "data-privacy-deletion-job",
            attributes: {}
          }
        };
        
        if (params.email) {
          payload.data.attributes.email = params.email;
        }
        
        if (params.phone_number) {
          payload.data.attributes.phone_number = params.phone_number;
        }
        
        if (params.profile_id) {
          payload.data.attributes.profile_id = params.profile_id;
        }
        
        const result = await klaviyoClient.post('/data-privacy-deletion-jobs/', payload);
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error requesting profile deletion: ${error.message}` }],
          isError: true
        };
      }
    },
  • Input schema using Zod for optional parameters: email, phone_number, profile_id.
    {
      email: z.string().email().optional().describe("Email of the profile to delete"),
      phone_number: z.string().optional().describe("Phone number of the profile to delete"),
      profile_id: z.string().optional().describe("ID of the profile to delete")
    },
  • Direct registration of the 'request_profile_deletion' tool via server.tool(), specifying schema, handler, and description.
      "request_profile_deletion",
      {
        email: z.string().email().optional().describe("Email of the profile to delete"),
        phone_number: z.string().optional().describe("Phone number of the profile to delete"),
        profile_id: z.string().optional().describe("ID of the profile to delete")
      },
      async (params) => {
        try {
          const payload = {
            data: {
              type: "data-privacy-deletion-job",
              attributes: {}
            }
          };
          
          if (params.email) {
            payload.data.attributes.email = params.email;
          }
          
          if (params.phone_number) {
            payload.data.attributes.phone_number = params.phone_number;
          }
          
          if (params.profile_id) {
            payload.data.attributes.profile_id = params.profile_id;
          }
          
          const result = await klaviyoClient.post('/data-privacy-deletion-jobs/', payload);
          return {
            content: [{ type: "text", text: JSON.stringify(result, null, 2) }]
          };
        } catch (error) {
          return {
            content: [{ type: "text", text: `Error requesting profile deletion: ${error.message}` }],
            isError: true
          };
        }
      },
      { description: "Request deletion of a profile for data privacy compliance" }
    );
  • src/server.js:44-44 (registration)
    Invocation of registerDataPrivacyTools on the main MCP server, which registers the request_profile_deletion tool among others.
    registerDataPrivacyTools(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