Skip to main content
Glama

get_profile

Retrieve a specific customer profile from Klaviyo using its unique ID to access contact details and marketing data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the profile to retrieve

Implementation Reference

  • Handler function that executes the get_profile tool: fetches profile data from Klaviyo API by ID and returns formatted JSON response or error.
    async (params) => {
      try {
        const profile = await klaviyoClient.get(`/profiles/${params.id}/`);
        return {
          content: [{ type: "text", text: JSON.stringify(profile, null, 2) }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error retrieving profile: ${error.message}` }],
          isError: true
        };
      }
    },
  • Input schema validation using Zod for the get_profile tool, requiring a string 'id' parameter.
    {
      id: z.string().describe("ID of the profile to retrieve")
    },
  • Tool registration call within registerProfileTools function, defining name, schema, handler, and description for get_profile.
    server.tool(
      "get_profile",
      {
        id: z.string().describe("ID of the profile to retrieve")
      },
      async (params) => {
        try {
          const profile = await klaviyoClient.get(`/profiles/${params.id}/`);
          return {
            content: [{ type: "text", text: JSON.stringify(profile, null, 2) }]
          };
        } catch (error) {
          return {
            content: [{ type: "text", text: `Error retrieving profile: ${error.message}` }],
            isError: true
          };
        }
      },
      { description: "Get a specific profile from Klaviyo" }
    );
  • src/server.js:32-32 (registration)
    Invocation of registerProfileTools to register all profile-related tools, including get_profile, on the MCP server.
    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