Skip to main content
Glama

update_profile

Update customer profile information in Klaviyo by modifying email, phone number, name, and custom properties for targeted marketing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the profile to update
emailNoEmail address of the profile
phone_numberNoPhone number of the profile
external_idNoExternal ID for the profile
first_nameNoFirst name of the profile
last_nameNoLast name of the profile
propertiesNoAdditional properties for the profile

Implementation Reference

  • Registration of the 'update_profile' MCP tool, including inline schema, handler function, and description.
    server.tool(
      "update_profile",
      {
        id: z.string().describe("ID of the profile to update"),
        email: z.string().email().optional().describe("Email address of the profile"),
        phone_number: z.string().optional().describe("Phone number of the profile"),
        external_id: z.string().optional().describe("External ID for the profile"),
        first_name: z.string().optional().describe("First name of the profile"),
        last_name: z.string().optional().describe("Last name of the profile"),
        properties: z.record(z.any()).optional().describe("Additional properties for the profile")
      },
      async (params) => {
        try {
          const { id, ...rest } = params;
          const attributes = {};
          
          // Add all provided fields to attributes
          for (const [key, value] of Object.entries(rest)) {
            if (value !== undefined && key !== 'properties') {
              attributes[key] = value;
            }
          }
          
          // Add properties if provided
          if (params.properties) {
            attributes.properties = params.properties;
          }
          
          const payload = {
            data: {
              type: "profile",
              id,
              attributes
            }
          };
          
          const result = await klaviyoClient.patch(`/profiles/${id}/`, payload);
          return {
            content: [{ type: "text", text: JSON.stringify(result, null, 2) }]
          };
        } catch (error) {
          return {
            content: [{ type: "text", text: `Error updating profile: ${error.message}` }],
            isError: true
          };
        }
      },
      { description: "Update an existing profile in Klaviyo" }
    );
  • The handler function that destructures parameters, builds the JSON:API payload for profile update, calls klaviyoClient.patch, and returns the result or error response.
    async (params) => {
      try {
        const { id, ...rest } = params;
        const attributes = {};
        
        // Add all provided fields to attributes
        for (const [key, value] of Object.entries(rest)) {
          if (value !== undefined && key !== 'properties') {
            attributes[key] = value;
          }
        }
        
        // Add properties if provided
        if (params.properties) {
          attributes.properties = params.properties;
        }
        
        const payload = {
          data: {
            type: "profile",
            id,
            attributes
          }
        };
        
        const result = await klaviyoClient.patch(`/profiles/${id}/`, payload);
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error updating profile: ${error.message}` }],
          isError: true
        };
      }
    },
    { description: "Update an existing profile in Klaviyo" }
  • Zod validation schema defining the input parameters for the 'update_profile' tool.
    {
      id: z.string().describe("ID of the profile to update"),
      email: z.string().email().optional().describe("Email address of the profile"),
      phone_number: z.string().optional().describe("Phone number of the profile"),
      external_id: z.string().optional().describe("External ID for the profile"),
      first_name: z.string().optional().describe("First name of the profile"),
      last_name: z.string().optional().describe("Last name of the profile"),
      properties: z.record(z.any()).optional().describe("Additional properties for the profile")
    },
  • The patch helper function used by the update_profile handler to make the HTTP PATCH request to Klaviyo API with retry logic.
    export async function patch(endpoint, data, fallbackFn) {
      return executeWithRetry(
        () => client.patch(endpoint, data),
        'PATCH',
        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