Skip to main content
Glama
ohneben

ActiveCampaign MCP

retrieve_contact_plus_append

Read-onlyIdempotent

Retrieve enriched data appended to a specific contact, including additional fields and attributes, using the contact ID. Supports pagination, sorting, and filtering.

Instructions

🟢 READ-ONLY · Contacts · GET /contacts/{id}/plusAppend

Retrieve a contacts plus append

Fetches data. Makes no changes to your ActiveCampaign account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the contact
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.
Behavior2/5

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

The description aligns with annotations (readOnlyHint, destructiveHint) but adds no extra behavioral insights beyond what annotations already provide. Missing details on pagination, rate limits, or returned data shape.

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 very short (three lines) but at the cost of clarity. It is structured with a header and summary but lacks sufficient detail. Could be improved without being significantly longer.

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?

No output schema provided, and the description does not explain what data is returned (e.g., what 'plus append' means). For a tool with 5 parameters including filters and pagination, more context is needed about how they affect results.

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% with all parameters described. The description does not add meaning beyond the schema. Baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Retrieve a contacts plus append' which is unclear; it doesn't explain what a 'plus append' is or how it differs from other contact retrieval tools like 'get_contact'. The purpose is vague.

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 like 'get_contact' or 'retrieve_contact_data'. The description only notes it's read-only, but does not specify appropriate contexts.

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