Skip to main content
Glama
ohneben

ActiveCampaign MCP

list_all_email_activities

Read-onlyIdempotent

Fetch all email activities with filters for subscriber or deal, pagination, and sorting. Read-only operation that does not modify data.

Instructions

🟢 READ-ONLY · Email Activities · GET /emailActivities

List all email activities

Fetches data. Makes no changes to your ActiveCampaign account.

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_dealIdNoSet this parameter to return only email activities belonging to a given deal. Sent to ActiveCampaign as "filters[dealId]".
filters_subscriberidNoSet this parameter to return only email activities belonging to a given subscriber. Sent to ActiveCampaign as "filters[subscriberid]".
Behavior3/5

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

Annotations already provide readOnlyHint, idempotentHint, and openWorldHint. The description adds 'Fetches data. Makes no changes' which aligns but does not disclose additional behavioral traits like pagination limits, response structure, or error cases. It provides no new context beyond the annotations.

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 plus the path. No wasted words. Front-loaded with read-only indicator and HTTP method. Efficient.

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 six parameters (including nested objects) and no output schema, the description is too brief. It lacks information about what an email activity is, response structure, or pagination behavior. Adequate but could be more helpful.

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 tool description does not need to add parameter details. It includes none, which is acceptable since the schema fully documents the six parameters. Baseline 3.

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 'List all email activities' and reinforces with 'Fetches data. Makes no changes.' The name and HTTP path are included, making the purpose unambiguous. It distinguishes from siblings like list_all_deal_activities or list_contact_activities by specifying email activities.

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 (e.g., list_contact_activities for contact-specific activities, or list_all_deal_activities for deal-related ones). The description does not mention exclusions, prerequisites, or comparison to siblings.

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