Skip to main content
Glama
ohneben

ActiveCampaign MCP

retrieve_all_lists

Read-onlyIdempotent

Retrieve all contact lists from your ActiveCampaign account, with options to filter by name and control sort order for efficient list management.

Instructions

๐ŸŸข READ-ONLY ยท Lists ยท GET /lists

Retrieve all lists

Fetches data. Makes no changes to your ActiveCampaign account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoLimit the number of returned results
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.
orders_nameNoOrders filtered results by weight, ascending order, or descending order. If weight is used, exact matches are returned first, followed by matches starting with what was filtered by, followed by the rest of the results. Sent to ActiveCampaign as "orders[name]".
filters_nameNoFilter by the name of the list Sent to ActiveCampaign as "filters[name]".
filters_name_operatorNoFilters lists by list name according to the operator specified. (See supported operators below) Sent to ActiveCampaign as "filters[name][<operator>]".
Behavior3/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 description's addition of 'Fetches data. Makes no changes' is redundant. It adds the HTTP method and a visual indicator (๐ŸŸข READ-ONLY), but no further behavioral details like pagination limits or rate limits.

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?

Extremely concise: three short lines with a clear hierarchy (icon, title, action statement). No fluff or redundant information.

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 no output schema, the description fails to mention that results are paginated or support filtering/sorting via the provided parameters. For a tool that can return many lists, this omission leaves the agent without key usage details.

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?

The input schema has 7 parameters with full descriptions (100% coverage). The tool description adds no additional meaning beyond the schema, so the baseline of 3 is appropriate.

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 'Retrieve all lists' and includes a read-only indicator and HTTP method. It explicitly says 'Fetches data. Makes no changes to your ActiveCampaign account.' This precisely identifies the action and resource, distinguishing it from write operations and single-list retrievals.

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 like 'retrieve_a_list' or 'list_all_accounts'. The description only states it retrieves all lists, but without context on use cases, prerequisites, 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.

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