Skip to main content
Glama
ohneben

ActiveCampaign MCP

find_contact_id_by_ac_playload

Read-onlyIdempotent

Searches an ActiveCampaign segment using a payload of conditions to return matching contact IDs.

Instructions

🟢 READ-ONLY · query · Segments · POST /api/3/segmentMatchSome/{segmentId}

Create a Match Some Request

Runs a search/report (a POST that returns data). Changes no account records; may create a short-lived, cached result-set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesRequest body (application/json).
pageNoPage Number1
sortNoComma delimited list of fields for which to sort the results. Optionally prepended with a dash sign to indicate descending order. Allowed fields: id, email, phone, first_name, last_name, full_name, cdate, udate, account_name, score, score<score-id>. The score<score-id> option will sort off of the value of a particular score. Examples: "email", "-phone", "score2", "last_name,-first_name"id
instantNoIf present, response will return instantly without waiting for the results to be ready
page_sizeNoPage Size. Maximum: 10,00020
segmentIdYessegmentId
Behavior4/5

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

Description adds valuable behavioral context beyond annotations by noting that the tool may create a short-lived cached result-set. This helps an agent understand side effects. No contradictions with annotations.

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 with two sentences plus a header. Every element provides value: the emoji and labels give quick context, and the sentences explain behavior and side effects without redundancy.

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

Completeness3/5

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

Given the complex nested input schema and no output schema, the description is minimal. It does not explain what the result-set contains (e.g., contact IDs) or how to interpret the response. For a query tool, more detail on return format would improve completeness.

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%, so parameters are fully documented in the schema. The description does not add extra meaning about specific parameters; it only mentions the endpoint and request type. 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 tool runs a search/report that returns data and does not modify records. It identifies the endpoint and read-only nature. However, the name 'find_contact_id_by_ac_playload' suggests a specific purpose (finding contact IDs), but the description does not mention contacts or IDs, creating slight ambiguity.

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 explicit guidance on when to use this tool versus siblings like 'create_match_all_request', 'create_match_one_request', or 'segment_match_check_by_external_id'. The description provides no context for choosing this tool over 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