Skip to main content
Glama
ohneben

ActiveCampaign MCP

list_variables

Read-onlyIdempotent

Fetch a list of personalization variables from your ActiveCampaign account with options to filter and sort by name, tag, format, content, or list name.

Instructions

🟢 READ-ONLY · Personalizations · GET /personalizations

List Variables

Fetches data. Makes no changes to your ActiveCampaign account.

Retrieve a list of personalization variables

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoResult limit (Default: 20)
offsetNoZero-based offset into the result set for pagination.
ordersNoSort order as an object, e.g. {"email":"ASC"} → orders[email]=ASC.
filtersNoField filters as an object, e.g. {"name":"ecom"} → filters[name]=ecom.
filter_tagNoFilter by variable tag Sent to ActiveCampaign as "filter[tag]".
orders_tagNoOrder variables by tag (ASC/DESC) Sent to ActiveCampaign as "orders[tag]".
filter_nameNoFilter by variable name Sent to ActiveCampaign as "filter[name]".
orders_nameNoOrder variables by name (ASC/DESC) Sent to ActiveCampaign as "orders[name]".
filter_formatNoFilter by tag format (html, text) Sent to ActiveCampaign as "filter[format]".
orders_formatNoOrder variables by format (ASC/DESC) Sent to ActiveCampaign as "orders[format]".
filter_contentNoContents of variable Sent to ActiveCampaign as "filter[content]".
orders_contentNoOrder variables by content (ASC/DESC) Sent to ActiveCampaign as "orders[content]".
filter_listNameNoFilter by name of list Sent to ActiveCampaign as "filter[listName]".
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds 'Fetches data, makes no changes' and a READ-ONLY badge, which is consistent but provides no additional behavioral context beyond what annotations convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded with the read-only badge and title. However, 'List Variables' is repeated, and the sentence 'Fetches data. Makes no changes.' is redundant given annotations. Still concise overall.

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

Completeness2/5

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

Despite 13 parameters, the description does not explain pagination (limit/offset), sort/filter behavior, or return format. No output schema exists, leaving the agent without critical usage context for a list operation.

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?

Input schema covers 100% of parameters with descriptions. The tool description itself adds no parameter meaning or usage context, so score is at baseline for high schema coverage.

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 clearly states the tool lists personalization variables with 'Retrieve a list of personalization variables' and includes the HTTP method. It distinguishes from sibling tools like 'list_all_contacts' by specifying the resource (variables).

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?

No guidance on when to use this tool versus alternatives (e.g., retrieve_variable for a single variable). The description does not mention use cases, prerequisites, or when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ohneben/ActiveCampaign-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server