Skip to main content
Glama
ohneben

ActiveCampaign MCP

list_all_tasks

Read-onlyIdempotent

Retrieve a list of all tasks in ActiveCampaign with filters for title, status, due date, assignee, and more. Fetches data without making changes.

Instructions

🟢 READ-ONLY · Deal Tasks · GET /dealTasks

List all tasks

Fetches data. Makes no changes to your ActiveCampaign account.

Retrieve a list of existing tasks

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_noteNoThe content describing the task Sent to ActiveCampaign as "filters[note]".
filters_relidNoThe id of the relational object for this task Sent to ActiveCampaign as "filters[relid]".
filters_titleNoThe title to be assigned to the task Sent to ActiveCampaign as "filters[title]".
filters_statusNoTask status means complete or incomplete. 1 is complete and 0 is incomplete. Sent to ActiveCampaign as "filters[status]".
filters_useridNoUser ID this task belongs to Sent to ActiveCampaign as "filters[userid]".
filters_duedateNoDue date of the task Sent to ActiveCampaign as "filters[duedate]".
filters_reltypeNoThe name of the relating object (see relationships table) Sent to ActiveCampaign as "filters[reltype]".
filters_due_afterNoFilter deal tasks that are due after a specific date Sent to ActiveCampaign as "filters[due_after]".
Fitlers_due_beforeNoFilter deal tasks that are due before a specific date Sent to ActiveCampaign as "Fitlers[due_before]".
filters_outcome_idNoThe id of a task outcome that the task belongs to. Sent to ActiveCampaign as "filters[outcome_id]".
filters_d_tasktypeidNoThe type of the task based on the available Task Types in the account Sent to ActiveCampaign as "filters[d_tasktypeid]".
filters_duedate_rangeNoFilter deal tasks that are due between specific date range (YYYY-MM-DD+YYYY-MM-DD format) or get categorized tasks (upcoming, scheduled, overdue values) Sent to ActiveCampaign as "filters[duedate_range]".
filters_assignee_useridNoThe id of the user a task is assigned to Sent to ActiveCampaign as "filters[assignee_userid]".
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds the HTTP method and that it fetches data without changes, but does not disclose pagination or other behaviors beyond what annotations provide.

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 relatively concise with two sentences, but contains slight redundancy between 'List all tasks' and 'Retrieve a list of existing tasks'. The emoji and endpoint line provide structure but one sentence could be removed.

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?

Given 17 parameters and no output schema, the description fails to mention pagination or that the result is a list. It leaves many important details unaddressed for a complex tool.

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?

All 17 parameters have descriptions in the input schema (100% coverage), so the description adds no additional parameter information beyond stating the tool lists tasks. 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 the verb 'List' and resource 'tasks', and includes the HTTP method. However, it does not explicitly differentiate from sibling tools like 'get_task' which retrieves a single task, though the scope is implied.

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 such as 'get_task', 'create_task', or other list tools. There is no mention of prerequisites or context.

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