Skip to main content
Glama
ohneben

ActiveCampaign MCP

get_result_set_by_id

Read-onlyIdempotent

Retrieve a segment's match-all result set by its segment and run IDs, checking readiness or error state.

Instructions

🟢 READ-ONLY · Segments · GET /api/3/segmentMatchAll/{segmentId}/{runId}

Return Match All result-set

Fetches data. Makes no changes to your ActiveCampaign account.

If the result-set is not ready yet, the response's is_ready attribute will be equal to false. The match-all request has errored out if the is_ready attribute is false and the run_id_end attribute contains a valid timestamp`; when this occurs please try your request again or alert the support team. If either the RunId or the SegmentId have expired or otherwise do not exist, a 404 with error details will be returned.

result-sets are cached and returned in the same sort order that's requ…

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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
runIdYesA run id
page_sizeNoPage Size. Maximum: 10,00020
segmentIdYessegmentId
Behavior4/5

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

Annotations already provide readOnlyHint and idempotentHint. The description adds valuable context: the response includes an 'is_ready' attribute, error conditions (404 for expired IDs), caching behavior, and sort order preservation. 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.

Conciseness4/5

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

The description is front-loaded with purpose and key details. It is fairly concise but includes minor formatting (emoji, bold) and some redundancy. Every sentence adds value, though it could be slightly shorter.

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 5 parameters (2 required) and no output schema, the description explains error states and readiness behavior well. It covers key aspects but lacks details on pagination and full response structure. Schema descriptions partially compensate.

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 description coverage is 100%, so baseline is 3. The description adds minimal extra meaning beyond the schema, only briefly touching on sort order. It does not elaborate on page, page_size, or the exact meaning of runId and segmentId beyond what's already in the schema.

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 tool 'Return Match All result-set', specifies it is READ-ONLY, and fetches data without making changes. It distinguishes from siblings by referencing the specific API endpoint and parameters (segmentId, runId).

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 implies usage for retrieving match-all result sets after a prior request, but does not explicitly tell when to use this tool vs alternatives like create_match_all_request or get_result_set_by_run_id. No exclusions or alternative tools are mentioned.

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