Skip to main content
Glama
ohneben

ActiveCampaign MCP

list_all_pipelines

Read-onlyIdempotent

Retrieve all pipelines from your ActiveCampaign account. Filter by title or stage presence, order by title or popularity, and paginate results.

Instructions

🟢 READ-ONLY · Deal Groups · GET /dealGroups

List all pipelines

Fetches data. Makes no changes to your ActiveCampaign account.

Retrieve all existing pipelines

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_titleNoOrder by Pipeline's title Sent to ActiveCampaign as "orders[title]".ASC
filters_titleNoFilter by pipeline's title. The filter matches any pipeline titles that contain the provided title (i.e. "Contact" matches all of "In Contact", "To Contact", and "Contact Pipeline"). Sent to ActiveCampaign as "filters[title]".
orders_popularNoOrder by number of deals each pipeline has. If pipelines have same number of deals, pipelines' created dates are used to determine the order. Sent to ActiveCampaign as "orders[popular]".ASC
filters_have_stagesNoFilter by whether pipelines have deal stages. Can be either `1` or `0`. If `1`, only pipelines with at least one stage will be returned. Sent to ActiveCampaign as "filters[have_stages]".
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description reinforces 'Fetches data. Makes no changes to your ActiveCampaign account,' adding no contradictions but providing additional endpoint context (Deal Groups, GET).

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?

The description is extremely concise: three short lines including an emoji label and endpoint info. Every sentence adds value, with no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 8 parameters including nested objects and no output schema, the description is somewhat brief but sufficient when combined with the annotated schema. It could mention pagination or result format, but the schema covers parameter details adequately.

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?

The input schema describes all 8 parameters with full coverage (100%). The description itself does not add parameter-level details beyond what the schema provides, so it meets the baseline of 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 explicitly states 'List all pipelines' and 'Retrieve all existing pipelines.' It also adds context with 'Deal Groups · GET /dealGroups,' clearly distinguishing it as a read-only listing operation among many sibling tools.

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 indicates it fetches data and makes no changes, making its read-only nature clear. While it does not provide explicit when-to-use or when-not-to-use guidance, the context of 'list all pipelines' is self-evident, and it adequately serves the purpose.

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