Klaviyo MCP

list_suppressed_profiles

Read-only

Fetch suppressed marketing profiles by reason (unsubscribe, hard bounce, spam complaint, user suppressed, or invalid email). Supports pagination via cursor; call once per reason for a complete list.

Instructions

List profiles suppressed from email marketing for a single reason. Klaviyo only allows equals (not any) for suppression.reason, so call once per reason if you need a full picture. Up to 100 per call. Use cursor for pagination.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "account": "<account>",
      "reason": "<reason>"
    },
    "name": "list_suppressed_profiles"
  }
}

Input Schema

Name	Required	Description
`reason`	Yes	Suppression reason. Required - Klaviyo allows only `equals` here.
`account`	Yes	Account name
`page_cursor`	No	Cursor from previous page.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds valuable behavioral context beyond that: the API's `equals`-only limitation, a 100-item page limit, and cursor-based pagination. No contradictions with annotations.

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?

Three concise sentences with zero filler. Purpose is front-loaded, followed by the key call pattern and pagination note. Every sentence contributes operational value.

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?

For a read-only listing tool with 3 documented parameters, annotations, and no output schema, the description covers purpose, reason restriction, page size, and pagination. It does not spell out the return payload shape, but 'List profiles' together with cursor-based pagination provides enough context for correct invocation.

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?

Schema description coverage is 100%, so the baseline is 3. The description repeats the `equals`-only constraint already present in the schema and adds little new meaning for `account` or `page_cursor`. It is adequate but does not significantly enrich parameter understanding.

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 names a specific verb ('List'), a specific resource ('profiles suppressed from email marketing'), and a clear scope ('for a single reason'). It immediately distinguishes itself from sibling list operations by focusing on suppressed profiles and the single-reason constraint.

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

Usage Guidelines5/5

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

It gives explicit operational guidance: call once per reason if a full picture is needed, because Klaviyo only supports `equals` for suppression.reason. This directly tells an agent how to use the tool correctly and when repeated calls are necessary.

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