Skip to main content
Glama
ohneben

ActiveCampaign MCP

list_contact_activities

Read-onlyIdempotent

Retrieve recent activities for a specific contact. Use after fetching a contact to view their latest actions and interactions.

Instructions

๐ŸŸข READ-ONLY ยท Activities ยท GET /activities

List a contact's activities

Fetches data. Makes no changes to your ActiveCampaign account.

View your contact's recent activity. The activity is generated when a contact is retrieved via /api/3/contacts/[contactID]. This endpoint should be used after retrieving a contact to obtain the latest data. This is useful for searching for contacts that match certain criteria - such as being part of a certain list, or having a specific custom field value.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoFilter for activities after a specific DateTime
limitNoNumber of results per page (ActiveCampaign default 20, max 100).
emailsNoFALSE: Excludes email data fields under each activity. No specific connection to emails is mentioned in the JSON data.โ€‹ TRUE: Returns deal activities that include email data fields like "connection_email." Each deal activity specifies the addition of email connection information along with timestamps and relevant metadata.
offsetNoZero-based offset into the result set for pagination.
ordersNoSort order as an object, e.g. {"email":"ASC"} โ†’ orders[email]=ASC.
contactNoRequired Contact ID
filtersNoField filters as an object, e.g. {"name":"ecom"} โ†’ filters[name]=ecom.
includeNoActivities to include: notes, notes.user, recipients, recipients.recipient, reference, reference.automation, reference.campaign, reference.campaign.campaignList, reference.campaign.campaignMessage, reference.campaignMessage, reference.contact, reference.contactList, reference.contactList.list, reference.deal, reference.deal.contact, reference.dealTasktype, reference.link, reference.list, reference.log, reference.log.campaign, reference.log.contact, reference.log.message, reference.message, reference.note, reference.sms, reference.sms.automation, useractivities to include
orders_tstampNoOrder activities by tstamp Sent to ActiveCampaign as "orders[tstamp]".
Behavior4/5

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

Annotations already provide readOnlyHint and destructiveHint. The description adds context that data is generated from contact retrieval and that no changes are made, aligning with annotations.

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 verbose with emoji and multiple paragraphs. It conveys necessary info but could be more 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?

With no output schema, the description fails to explain the return structure or specific fields of activities, leaving a gap for an agent to understand how results are formatted.

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 descriptions cover 100% of parameters with details. The description adds no extra parameter-level meaning beyond high-level usage, so a 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 it lists a contact's activities, uses a read-only indicator, and explains the context (after retrieving a contact). It distinguishes from siblings by focusing on activities generated from contact retrieval.

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

Usage Guidelines4/5

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

The description specifies when to use the tool (after retrieving a contact) and its usefulness for searching contacts. However, it does not explicitly exclude alternative tools or provide when-not-to-use guidance.

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