Skip to main content
Glama

Klaviyo

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Klaviyo List Profiles

klaviyo_list_profiles
Read-onlyIdempotent

Search contacts by email, name, or custom attributes. Returns profile IDs, emails, names, and properties with pagination support.

Input Schema

NameRequiredDescriptionDefault
filterNoFilter string in Klaviyo filter syntax (e.g., "equals(email,\"user@example.com\")")
_apiKeyYesKlaviyo private API key
page_sizeNoNumber of profiles per page (default 20, max 100)

Output Schema

NameRequiredDescriptionDefault
dataNoArray of profile objects
linksNoPagination links

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Array of profile objects",
+      "items": {
+        "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"
+              },
+              "phone_number": {
+                "description": "Contact phone number",
+                "type": "string"
+              },
+              "properties": {
+                "description": "Custom properties",
+                "type": "object"
+              }
+            },
+            "type": "object"
+          },
+          "id": {
+            "description": "Profile ID",
+            "type": "string"
+          },
+          "type": {
+            "description": "Resource type (profile)",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "links": {
+      "description": "Pagination links",
+      "properties": {
+        "next": {
+          "description": "Next page link",
+          "type": "string"
+        },
+        "prev": {
+          "description": "Previous page link",
+          "type": "string"
+        },
+        "self": {
+          "description": "Self link",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-klaviyo-api-key"
+  },
+  {
+    "_apiKey": "your-klaviyo-api-key",
+    "filter": "equals(email,\"user@example.com\")",
+    "page_size": 50
+  }
+]
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

The description discloses return fields (profile IDs, emails, names, properties) and pagination support, which adds context beyond the annotations' read-only and idempotent flags. It doesn't contradict annotations and provides useful behavioral details.

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 is two sentences, front-loaded with the action and resource, with no unnecessary words. It is concise and well-structured.

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

Completeness4/5

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

Given the tool's simplicity, the description covers the main purpose, return values, and pagination. The output schema handles details, and annotations cover safety, so this is adequately complete for selection and invocation.

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

Parameters4/5

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

The schema already documents all three parameters with descriptions. The description adds that filtering can be done by email, name, or custom attributes, which enriches the generic filter parameter and clarifies intended usage.

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 states 'Search contacts by email, name, or custom attributes,' which is a specific verb (search) and resource (contacts). This clearly distinguishes from sibling tools like klaviyo_get_profile (single profile) and klaviyo_list_lists (lists).

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

Usage Guidelines2/5

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

The description provides no explicit guidance on when to choose this tool over alternatives. It only states what it does, leaving the agent to infer usage without exclusions or alternative recommendations.

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