Skip to main content
Glama

delete_profile

Remove a customer profile from Klaviyo marketing automation by providing its unique identifier.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the profile to delete

Implementation Reference

  • Handler function that performs the deletion by calling klaviyoClient.del on the profiles endpoint.
    async (params) => {
      try {
        await klaviyoClient.del(`/profiles/${params.id}/`);
        return {
          content: [{ type: "text", text: "Profile deleted successfully" }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error deleting profile: ${error.message}` }],
          isError: true
        };
      }
    },
  • Zod schema defining the input parameter 'id' for the tool.
    {
      id: z.string().describe("ID of the profile to delete")
    },
  • Registration of the delete_profile tool via server.tool call.
    server.tool(
      "delete_profile",
      {
        id: z.string().describe("ID of the profile to delete")
      },
      async (params) => {
        try {
          await klaviyoClient.del(`/profiles/${params.id}/`);
          return {
            content: [{ type: "text", text: "Profile deleted successfully" }]
          };
        } catch (error) {
          return {
            content: [{ type: "text", text: `Error deleting profile: ${error.message}` }],
            isError: true
          };
        }
      },
      { description: "Delete a profile from Klaviyo" }
    );
  • Supporting del function in Klaviyo client that handles the HTTP DELETE request with retry logic and error handling.
    export async function del(endpoint, data, fallbackFn) {
      return executeWithRetry(
        () => {
          const config = data ? { data } : undefined;
          return client.delete(endpoint, config);
        },
        'DELETE',
        endpoint,
        data,
        fallbackFn
      ).then(response => {
        // For DELETE requests that return 204 No Content
        if (response === undefined) {
          return { success: true };
        }
        return response;
      });
    }
  • src/server.js:32-32 (registration)
    Call to registerProfileTools which includes the delete_profile tool registration.
    registerProfileTools(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