Skip to main content
Glama
ohneben

ActiveCampaign MCP

get_saved_segment_summaries

Read-onlyIdempotent

Retrieve summary listings of saved segments from your ActiveCampaign account, supporting search, sorting, and pagination.

Instructions

🟢 READ-ONLY · Segments · GET /audiences

List Summaries for Saved Segments

Fetches data. Makes no changes to your ActiveCampaign account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage Number
sortNoSingle sort value. Dash sign indicates descending order-updated_date
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.
searchNoSearch for Saved Segments by name. Not case sensitive
filtersNoField filters as an object, e.g. {"name":"ecom"} → filters[name]=ecom.
page_sizeNoPage Size
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false; description adds 'READ-ONLY' and 'Fetches data' but doesn't expand on return structure or pagination behavior.

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?

Description is very short (one sentence plus header); could be trimmed but overall efficient.

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?

Lacks explanation of what 'summaries' means vs full segment data, no output schema, and does not clarify pagination behavior beyond schema, especially with 8 parameters.

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 covers 100% of parameters with descriptions; description adds no additional parameter details, so baseline score of 3 applies.

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?

Description clearly states 'List Summaries for Saved Segments' and 'Fetches data', but doesn't differentiate from sibling get_saved_segment_summaries_by_id or list_all_segments.

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

Usage Guidelines3/5

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

Provides basic context ('Fetches data. Makes no changes.') but no guidance on when to use this vs alternatives.

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