Klaviyo MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 41 tools
Many tools follow a plural/singular pattern for list vs single resource, which helps distinguish them. However, tools like delete_profile and request_profile_deletion appear to overlap, and pairs like get_metric/get_metrics rely on naming convention alone without descriptions, creating potential misselection.
Most tools use a consistent verb_noun pattern (get, create, update, delete, add), and plural/singular nouns generally indicate list vs single. Inconsistencies exist, such as add_profiles_to_list (plural) vs add_tag_to_resource (singular), and request_profile_deletion deviates from the delete_* style.
With 41 tools, the server is well above the typical 3-15 range. Many resources have both plural and singular getters, inflating the count, and the broad scope makes it feel heavy rather than well-scoped.
The server provides extensive read operations but lacks update/delete for many resources (lists, segments, templates, catalogs, etc.), no remove_tag_from_resource, and no update operations for webhooks or coupons. This leaves significant lifecycle gaps for a CRUD-style API.