Klaviyo MCP

flow_series_report

Read-only

Get time-series metrics for Klaviyo flows, bucketed by hourly, daily, weekly, or monthly intervals. Analyze conversion performance over preset or custom date ranges to identify trends.

Instructions

Time-series flow (automation) metrics for a Klaviyo account. Buckets by interval. Rate limited: 2/min.

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

Input Schema

Name	Required	Description
`end`	No	Custom range end, YYYY-MM-DD. Defaults to today.
`year`	No	Year for quarter, e.g. 2024.
`start`	No	Custom range start, YYYY-MM-DD. Overrides timeframe. Data floor: 2023-06-01 (earlier is clamped).
`account`	Yes	Account name
`quarter`	No	Quarter 1-4 (with year) - convenience for a full quarter.
`interval`	No
`timeframe`	No
`conversion_metric_id`	Yes	Placed Order metric ID.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 8, 2026

TDQS

A3.5/5.0

Behavior4/5

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

The annotations already establish readOnlyHint and openWorldHint, and the description adds valuable behavioral context: 'Buckets by interval' describes the operation's shape, and 'Rate limited: 2/min' discloses a concrete operational constraint. This goes beyond the annotations without contradicting them.

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 extremely concise and front-loaded. The first sentence states the core purpose and behavior; the second sentence adds the critical rate limit. Every word earns its place, and no redundant phrasing exists.

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 an 8-parameter tool with no output schema, this description is minimal but not wholly inadequate. It conveys the resource, the batching behavior, and a rate limit, while the schema fills in parameter details. However, it does not describe what the returned series looks like, how to choose between timeframe and custom ranges, or when to prefer this over sibling reporting tools, leaving clear gaps for an agent.

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 75%, so most parameters are already explained. The description adds minor semantic value by framing the tool as interval-bucketed time-series data, which supports interval and timeframe, but it does not clarify required parameters or the relationship between timeframe and custom start/end. The schema carries the main burden, and the description does not meaningfully compensate for the remaining gaps.

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 identifies the resource as time-series flow/automation metrics for a Klaviyo account and adds the distinguishing mechanism 'Buckets by interval.' It lacks an explicit verb but the title annotation provides 'Get,' and the meaning is transparent. It does not explicitly differentiate itself from sibling tools like flow_report, so it falls short of a 5.

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 flow_report or metric_aggregate. The rate-limit note is a constraint, not a usage guideline. There are no stated exclusions, prerequisites, or context that would help an agent choose this tool over a sibling.

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