Skip to main content
Glama
ohneben

ActiveCampaign MCP

list_all_orders

Read-onlyIdempotent

Fetch all e-commerce orders, filterable by connection ID, customer, email, state, and external date, with sorting and pagination.

Instructions

🟢 READ-ONLY · Ecom Orders · GET /ecomOrders

List all orders

Fetches data. Makes no changes to your ActiveCampaign account.

List all existing e-commerce order 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.
orders_emailNoOrder by email. Accepted values are ASC or DESC. Sent to ActiveCampaign as "orders[email]".
orders_stateNoOrder by state. Accepted values are ASC or DESC. Sent to ActiveCampaign as "orders[state]".
filters_emailNoFilter by the customer email address. Sent to ActiveCampaign as "filters[email]".
filters_stateNoFilter by the state of the order. 0 = Pending, 1 = Completed, 2 = Abandoned, 3 = Recovered, 4 = Waiting (Customer checked out but payment is not yet completed) Sent to ActiveCampaign as "filters[state]".
orders_customeridNoOrder by customer ID. Accepted values are ASC or DESC. Sent to ActiveCampaign as "orders[customerid]".
orders_externalidNoOrder by external ID. Accepted values are ASC or DESC. Sent to ActiveCampaign as "orders[externalid]".
filters_customeridNoFilter by the customer id Sent to ActiveCampaign as "filters[customerid]".
filters_externalidNoFilter by the external id of the order. Sent to ActiveCampaign as "filters[externalid]".
orders_connectionidNoOrder by connection ID. Accepted values are ASC or DESC. Sent to ActiveCampaign as "orders[connectionid]".
filters_connectionidNoFilter by the connection id. Must be greater than 0. Sent to ActiveCampaign as "filters[connectionid]".
orders_externalcheckoutidNoOrder by external checkout ID. Accepted values are ASC or DESC. Sent to ActiveCampaign as "orders[externalcheckoutid]".
filters_externalcheckoutidNoFilter by the external checkout id Sent to ActiveCampaign as "filters[externalcheckoutid]".
orders_external_created_dateNoOrder by external created date. Accepted values are ASC or DESC. Sent to ActiveCampaign as "orders[external_created_date]".
filters_external_created_dateNoFilter by the external created date Sent to ActiveCampaign as "filters[external_created_date]".
Behavior3/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, destructiveHint. The description adds that it makes no changes and is a GET request, which is consistent but does not add significant new behavioral context beyond annotations.

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. However, it repeats 'List all orders' twice and has extra symbols (🟢, ·). Still, it is efficient and easily scanned.

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 18 optional parameters and no output schema, the description does not mention pagination, filtering capabilities, or how to use the parameters effectively. The schema covers details, but the description could summarize key usage patterns.

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 fully documents each parameter. The description does not add any additional meaning or examples for parameters. Baseline 3 is appropriate.

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 it lists all orders and is read-only. It mentions the endpoint and that it fetches data without making changes. However, it does not explicitly distinguish from sibling tools like 'get_order', though the name and context imply it.

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. There is no mention of prerequisites, exclusions, or when not to use it. Given many sibling tools for orders, 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