Skip to main content
Glama

Klaviyo

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Klaviyo Get Profile

klaviyo_get_profile
Read-onlyIdempotent

Get a contact's full profile by ID. Returns email, name, phone, custom properties, list memberships, and subscription status.

Input Schema

NameRequiredDescriptionDefault
_apiKeyYesKlaviyo private API key
profile_idYesKlaviyo profile ID

Output Schema

NameRequiredDescriptionDefault
dataNoProfile object

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Profile object",
+      "properties": {
+        "attributes": {
+          "description": "Profile attributes",
+          "properties": {
+            "email": {
+              "description": "Contact email address",
+              "type": "string"
+            },
+            "first_name": {
+              "description": "Contact first name",
+              "type": "string"
+            },
+            "last_name": {
+              "description": "Contact last name",
+              "type": "string"
+            },
+            "list_memberships": {
+              "description": "List memberships",
+              "items": {
+                "type": "object"
+              },
+              "type": "array"
+            },
+            "phone_number": {
+              "description": "Contact phone number",
+              "type": "string"
+            },
+            "properties": {
+              "description": "Custom properties",
+              "type": "object"
+            },
+            "subscriptions": {
+              "description": "Subscription status",
+              "items": {
+                "type": "object"
+              },
+              "type": "array"
+            }
+          },
+          "type": "object"
+        },
+        "id": {
+          "description": "Profile ID",
+          "type": "string"
+        },
+        "type": {
+          "description": "Resource type (profile)",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-klaviyo-api-key",
+    "profile_id": "01ARZ3NDEKTSV4RRFFQ69G5FAV"
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly and idempotent, so the safety profile is covered. The description adds valuable behavioral context by listing the fields returned ('email, name, phone, custom properties, list memberships, and subscription status'), which enriches understanding of what the tool does beyond the annotations. It does not discuss rate limits or potential pitfalls, but with strong annotations this is sufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description consists of two clear, front-loaded sentences. The first sentence states the core purpose, and the second summarizes the return value. There is no extraneous information, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (get by ID) and the description, combined with the annotations and the presence of an output schema, provides sufficient context. It tells the user exactly what data will be returned, making the description complete for a read-only lookup tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema provides 100% coverage with descriptions for both parameters ('Klaviyo private API key' and 'Klaviyo profile ID'). The description itself does not elaborate on the parameters, aligning with the baseline 3 for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: 'Get a contact's full profile by ID.' This specifies the action (get), the resource (contact's full profile), and the method (by ID). It distinguishes from sibling tools like klaviyo_list_profiles which lists profiles, by emphasizing single-profile retrieval via a specific identifier.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use the tool: when you have a profile ID and need a comprehensive profile. It clearly indicates the need for an ID, which is a clear context. However, it does not explicitly name alternatives or provide exclusion criteria, stopping short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Klaviyo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources