Skip to main content
Glama
ohneben

ActiveCampaign MCP

list_all_deal_activities

Read-onlyIdempotent

Retrieve deal activities filtered by deal ID, data type, and pagination, with the option to exclude email activities.

Instructions

🟢 READ-ONLY · Deal Activities · GET /dealActivities

List all deal activities

Fetches data. Makes no changes to your ActiveCampaign account.

View a recent activity for Deals. A specific deal's activity can also be viewed using /api/3/deals/[dealID]/dealActivities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dealNoFilter by deal ID
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.
exclude_emailNoInclude this param to exclude "email", "connection_email", and "LinkData" activity types Sent to ActiveCampaign as "exclude=email".
filters_data_idNoEnter any dataId (see Response details) to filter by related object. Example "291" for a note with ID 291 Sent to ActiveCampaign as "filters[data_id]".
filters_data_typeNoEnter any dataType (see Response Details) to filter by that type. Examples: "userid" or task" or "note" Sent to ActiveCampaign as "filters[data_type]".
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. The description adds that it is read-only and makes no changes, which is consistent but adds no extra behavioral detail 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.

Conciseness3/5

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

The description is somewhat repetitive (e.g., 'List all deal activities' appears twice) and could be more streamlined. It is functional but not optimally 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 good annotations and schema, the description fails to explain the return structure or pagination behavior. With 8 parameters and no output schema, the description should provide more context on what the tool returns.

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 coverage is 100% (8 parameters all with descriptions). The description adds no parameter-level context; it does not mention any parameters or how to use them. 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?

The description clearly states 'List all deal activities' and explicitly mentions the GET endpoint and read-only nature. It distinguishes from a specific alternative endpoint for a single deal's activities, clarifying scope.

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 provides context that this tool lists all deal activities and mentions a specific alternative endpoint for filtering by deal ID. However, it does not explicitly state when to use this tool versus other sibling tools like list_all_deals or retrieve_a_deal.

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