Skip to main content
Glama

Get a campaign's A/B results

get_campaign_ab_test_results
Read-only

Use this when the user asks which variant of an A/B split is doing better. For each split step it returns the variants and their weights, and how each did in all and since the weights last changed: leads, invitations sent and accepted, replies, positive replies, meetings, bounces and unsubscribes, with rates, and replies by day. Free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "campaignId": "<campaignId>"
    },
    "name": "get_campaign_ab_test_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoCount only the leads that reached a split at or before this ISO 8601 date-time, not before `since`.
sinceNoCount only the leads that reached a split at or after this ISO 8601 date-time.
timezoneNoThe IANA time zone whose days `replySeries` counts by, such as `Europe/Lisbon`. UTC by default.UTC
campaignIdYesThe campaign's id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine value beyond them: the response is organized per split step, metrics are reported both 'in all' and 'since the weights last changed', and the call is free — the dual-window reporting is non-obvious behavior an agent could not infer.

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?

Two sentences, front-loaded with the selection trigger and followed by a dense but scannable metric list. The long enumeration is justified because there is no output schema to describe the return payload, though it could be grouped more tightly.

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?

With no output schema, the description carries the burden of explaining returns and does so well by listing the metric families and per-day reply series. Minor gaps remain: no mention of what happens when a campaign has no A/B splits, and no hint at the response nesting (per step, per variant).

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 the schema already explains campaignId, since, to, and timezone in detail. The description only indirectly touches parameters via 'since the weights last changed' and 'replies by day' (which maps to timezone), so it stays at the baseline rather than adding syntax or constraint detail.

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 names a specific verb-plus-resource outcome: per-split-step variant performance for an A/B test, and enumerates the metrics returned. It is clearly distinguishable from aggregate siblings like get_campaign_stats, though it does so through the trigger sentence rather than explicit sibling naming.

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

Usage Guidelines4/5

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

It gives an explicit trigger — 'use this when the user asks which variant of an A/B split is doing better' — which is a real selection rule. It lacks any when-not guidance or named alternative (e.g., for overall campaign numbers use get_campaign_stats), and 'Free' is a helpful but incidental cost note.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources