Skip to main content
Glama
ohneben

ActiveCampaign MCP

create_match_all_request

Read-onlyIdempotent

Initiate a match-all request to find all contacts matching a segment. Results are returned within seconds, or a run ID is provided for later polling.

Instructions

🟢 READ-ONLY · query · Segments · POST /api/3/segmentMatchAll

Create a Match All Request for a new Segment

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

Find all Contact Id's that match the given Segment. The provided segment will be saved with a 24 hour TTL. A new match-all request will be initiated. If results are not ready within 4 seconds, a response that lacks a result-set will be returned. Use the returned segmentId and runId to poll and check back later to see if the result-set is ready.

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>, field<custom-field-id>. The score<score-id> option will sort off of the value of a particular score. The field<custom-field-id> option will sort off of the value of a particular custom field.id
instantNoIf present, API will return instantly with a runId without waiting for up to 4 seconds for the results to be ready. Useful if you want to kick off a match-all request but don't need the results immediately
page_sizeNoPage Size. Maximum: 10,00020
Behavior5/5

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

Annotations already declare readOnlyHint and destructiveHint, and the description adds valuable behavioral details: it creates a short-lived cached result-set, has a 24-hour TTL, a 4-second timeout, and requires polling. No contradiction 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is concise (4 sentences) and front-loaded with key information. However, it could be slightly more compact without losing clarity.

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?

Despite no output schema, the description explains the asynchronous behavior, polling mechanism, and returned segmentId and runId. This is sufficient for a complex tool, though more detail on the response format would help.

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 the parameters are well-documented in the schema. The tool description does not add extra meaning to parameters, which is acceptable. Baseline score is appropriate.

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 clearly states the action 'Create a Match All Request for a new Segment' and the resource. The title and emoji reinforce the read-only nature. It distinguishes from the sibling 'create_match_all_request_with_segment_id' by emphasizing 'new Segment'.

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?

The description explains when to use this tool (to find all Contact IDs matching a new segment), but does not explicitly mention when not to use it or compare with alternatives like create_match_one_request or using an existing segment ID. The polling guidance is helpful but not a full usage guideline.

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