Skip to main content
Glama
ohneben

ActiveCampaign MCP

list_all_customers

Read-onlyIdempotent

Retrieve all e-commerce customer resources from ActiveCampaign. Filter by email, external ID, or connection ID, and control pagination with limit and offset.

Instructions

🟢 READ-ONLY · Ecom Customers · GET /ecomCustomers

List all customers

Fetches data. Makes no changes to your ActiveCampaign account.

List all e-commerce customer resources.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results per page (ActiveCampaign default 20, max 100).
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.
filters_emailNoFilter by the email address of a customer. Sent to ActiveCampaign as "filters[email]".
filters_externalidNoFilter by the id of the customer in the external service. Sent to ActiveCampaign as "filters[externalid]".
filters_connectionidNoFilter by the id of the connection object for the service where the customer originates. Sent to ActiveCampaign as "filters[connectionid]".
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. The description adds 'Fetches data. Makes no changes.' which aligns but does not disclose additional behavioral traits beyond the endpoint method. Average value added.

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

Conciseness3/5

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

The description is somewhat repetitive (e.g., 'List all customers' vs 'List all e-commerce customer resources') and includes an emoji and endpoint notation. Could be more concise without losing clarity.

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

Completeness3/5

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

With no output schema and 7 parameters, the description only covers the high-level function. Annotations provide safety context, but the description does not explain pagination, output format, or edge cases. Minimal completeness.

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?

Schema description coverage is 100%, so the schema already documents all parameters. The description adds no information about parameters or how to use them, meeting the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists all customers, specifying 'Ecom Customers' and the endpoint path. It's unambiguous but does not differentiate from other list tools for different entities among the many siblings.

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 explicit guidance on when to use this tool versus alternatives. The description only states what it does, not when to use it or when not to. Given the large number of sibling tools, this is a gap.

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