Klaviyo MCP

list_recent_events

Read-only

Retrieve recent events from a Klaviyo account, optionally filtered by a metric like Placed Order. Returns up to 100 events per page with pagination support.

Instructions

List recent events for a Klaviyo account, optionally filtered by metric_id (e.g. Placed Order). Returns up to 100 most recent.

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>"
    },
    "name": "list_recent_events"
  }
}

Input Schema

Name	Required	Description
`account`	Yes	Account name
`metric_id`	No	Filter to events for one metric.
`page_size`	No	Default 25, maximum 100 per page.
`page_cursor`	No	Cursor from the previous page.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 8, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds useful context about returning up to 100 most recent events and optional metric filtering. However, it does not disclose pagination behavior, data freshness, or any account-level requirements beyond what the schema already specifies.

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 a single concise sentence that front-loads the main action and resource, and includes a useful example. Every word contributes meaning, and there is no redundancy with the schema or annotations.

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

Completeness3/5

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

For a tool with four parameters, no output schema, and no usage guidance, the description is minimally adequate. It covers the core purpose and a key return characteristic, but it does not describe the event object shape, pagination workflow, or when a user should choose this over related reporting tools.

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 schema already documents all parameters clearly. The description adds a concrete example for metric_id ('Placed Order') and a result limit hint, but these are minor enhancements beyond the schema. Baseline 3 is appropriate.

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

Purpose4/5

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

The description clearly states a specific verb and resource: 'List recent events for a Klaviyo account.' The optional metric_id filter adds relevant detail. It does not explicitly distinguish itself from sibling tools like metric_aggregate, but the intent is understandable from the name and description.

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 guidance on when to use this tool versus alternatives such as metric_aggregate or list_metrics. It implies usage by describing the return of recent events and optional metric filtering, but there are no explicit use cases, exclusions, or comparisons to sibling tools.

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