Skip to main content
Glama
ohneben

ActiveCampaign MCP

list_all_contacts

Read-onlyIdempotent

Retrieve and filter contacts by criteria such as email, list, tag, or date. Search for specific contacts or list all contacts in your ActiveCampaign account.

Instructions

🟢 READ-ONLY · Contacts · GET /contacts

List, search, and filter contacts

Fetches data. Makes no changes to your ActiveCampaign account.

Use this API endpoint to list all contacts, search contacts, or filter contacts by many criteria. For example, search for specific contacts by email, list, account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoFilter contacts by ID. Can be repeated for multiple IDs. Example: ids[]=1&ids[]=2&ids[]=42
emailNoEmail address of the contact you want to get
limitNoNumber of results per page (ActiveCampaign default 20, max 100).
phoneNoFilter contacts where the phone number starts with the given value
tagidNoFilter contacts associated with the given tag
formidNoFilter contacts associated with the given form
listidNoFilter contacts associated with the given list
offsetNoZero-based offset into the result set for pagination.
ordersNoSort order as an object, e.g. {"email":"ASC"} → orders[email]=ASC.
searchNoFilter contacts that match the given value in the contact names, organization, phone or emailnull
statusNoSee [available values](https://developers.activecampaign.com/reference/contact)
waitidNoFilter by contacts in the wait queue of an automation block
excludeNoExclude from the response the contact with the given ID
filtersNoField filters as an object, e.g. {"name":"ecom"} → filters[name]=ecom.
id_lessNoOnly include contacts with an ID less than the given ID
seriesidNoFilter contacts associated with the given automation
orders_idNoOrder contacts by unique ID Sent to ActiveCampaign as "orders[id]".ASC
segmentidNoReturn only contacts that match a list segment (the first call kicks off an asynchronous query. When the query is complete, subsequent API calls will return contacts that match the segment - timeout 1hr)
email_likeNoFilter contacts that contain the given value in the email address
id_greaterNoOnly include contacts with an ID greater than the given ID
orders_nameNoOrder contacts by full name Sent to ActiveCampaign as "orders[name]".
orders_cdateNoOrder contacts by creation date Sent to ActiveCampaign as "orders[cdate]".
orders_emailNoOrder contacts by email Sent to ActiveCampaign as "orders[email]".ASC
orders_scoreNoOrder contacts by score Sent to ActiveCampaign as "orders[score]".
organizationNo(Deprecated) Please use Account-Contact end points. Filter contacts associated with the given organization ID
in_group_listsNoSet this to "true" in order to return only contacts that the current user has permissions to see.
orders_last_nameNoOrder contacts by last name Sent to ActiveCampaign as "orders[last_name]".
orders_first_nameNoOrder contacts by first name Sent to ActiveCampaign as "orders[first_name]".
filters_created_afterNoFilter contacts that were created after this date Sent to ActiveCampaign as "filters[created_after]".
filters_updated_afterNoFilter contacts that were updated after this date Sent to ActiveCampaign as "filters[updated_after]".
filters_created_beforeNoFilter contacts that were created prior to this date Sent to ActiveCampaign as "filters[created_before]".
filters_updated_beforeNoFilter contacts that were updated before this date Sent to ActiveCampaign as "filters[updated_before]".
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. Description reinforces 'READ-ONLY' and 'Makes no changes.' It adds minimal extra behavioral context (e.g., pagination hinted via parameters but not described). No contradiction.

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?

Description is short and front-loaded with key info. Uses visual marker (🟢) and clear categorization. Could be more structured (e.g., bullet points) but sufficiently concise.

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 having 32 parameters and no output schema, the description does not explain pagination, response format, rate limits, or how to handle large result sets. Agent may need additional context for effective use.

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?

All 32 parameters have descriptions in the schema (100% coverage). Description only provides examples of searching by email, list, account, adding marginal value beyond schema. Baseline 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?

Description clearly states 'List, search, and filter contacts' with specific verb and resource. The emoji and 'READ-ONLY' text immediately convey the action. Distinguishes from sibling tools by explicitly targeting contacts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description gives examples of use cases (search by email, list, account) but does not specify when not to use or contrast with alternatives like get_contact or retrieve_contact_data. Implies usage for general listing and filtering.

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