Skip to main content
Glama

Klaviyo

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Klaviyo List Campaigns

klaviyo_list_campaigns
Read-onlyIdempotent

Search campaigns by status (draft, scheduled, sent). Returns campaign IDs, names, status, send dates, and performance metrics.

Input Schema

NameRequiredDescriptionDefault
filterNoFilter by status (e.g., "equals(messages.channel,\"email\")")
_apiKeyYesKlaviyo private API key

Output Schema

NameRequiredDescriptionDefault
dataNoArray of campaign 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 campaign objects",
+      "items": {
+        "properties": {
+          "attributes": {
+            "description": "Campaign attributes",
+            "properties": {
+              "created_at": {
+                "description": "Creation timestamp",
+                "type": "string"
+              },
+              "name": {
+                "description": "Campaign name",
+                "type": "string"
+              },
+              "scheduled_at": {
+                "description": "Scheduled send time",
+                "type": "string"
+              },
+              "sent_at": {
+                "description": "Actual send time",
+                "type": "string"
+              },
+              "status": {
+                "description": "Campaign status (draft, scheduled, sent)",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "id": {
+            "description": "Campaign ID",
+            "type": "string"
+          },
+          "type": {
+            "description": "Resource type (campaign)",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "links": {
+      "description": "Pagination links",
+      "properties": {
+        "next": {
+          "description": "Next 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(status,\"sent\")"
+  }
+]
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds value by specifying the response contents (campaign IDs, names, status, send dates, performance metrics), which goes beyond the structured metadata. It does not mention pagination or API-specific quirks, but this is acceptable given the annotation coverage.

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?

A single, front-loaded sentence conveys the purpose, key filter dimension, and return values. There is no redundancy or irrelevant detail, making it highly efficient.

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 (two parameters, one required), has full schema coverage, and has an output schema. The description covers the essential behavior and return summary. There are no significant gaps that would hinder correct 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?

Schema coverage is 100%, so parameter basics are already documented. The description adds meaning by clarifying that the filter is primarily for status and enumerating the status values (draft, scheduled, sent), which aligns with the filter parameter's purpose beyond the schema example.

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 uses a specific verb ('Search') and a resource ('campaigns'), and clearly states the filtering dimension (status: draft, scheduled, sent) and the returned fields. This distinguishes it from sibling tools like klaviyo_get_campaign (single campaign) and klaviyo_list_lists/profiles (other resources).

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 the tool is used when searching campaigns by status and lists the applicable statuses. It does not explicitly mention alternatives or exclusions, but the context is clear enough for an agent to choose this tool over the sibling 'get_campaign' tool.

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