Skip to main content
Glama
Sign In

MailBeast.ai

by ai.mailbeast
OverviewDiscussionsAdmin

Campaign analytics

get_campaign_analytics
Read-onlyIdempotent

Campaign performance for a period: sent, delivered, opens, clicks, replies, bounces, unsubscribes and rates. A campaign with subsequences is counted together with them by default (each email and person once); scope: "main" limits it to the main sequence, subsequenceId to one subsequence. breakdown adds per-mailbox (smtp), per-step/variant (sequence) or per-bounce-type (bounce) tables. Pass interval to also get a time series by day/week/month.

Input Schema

NameRequiredDescriptionDefault
idYesCampaign id (UUID).
scopeNo`family` (default): the campaign with its subsequences. `main`: the main sequence only.
endDateNoLast day, ISO date (YYYY-MM-DD). Defaults to today. Only used together with startDate.
intervalNoAlso return a time series at this granularity (long windows may be returned coarser).
breakdownNo
startDateNoFirst day, ISO date (YYYY-MM-DD), whole days in the workspace timezone. Without startDate the window is the LAST 7 DAYS (endDate alone is ignored). Clipped to the plan retention.
excludeOOONoExclude out-of-office auto-replies from reply counts.
subsequenceIdNoOnly this subsequence of the campaign (id from list_subsequences); overrides `scope` (UUID).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / scope
      Added value: +{
+  "description": "`family` (default): the campaign with its subsequences. `main`: the main sequence only.",
+  "enum": [
+    "family",
+    "main"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / subsequenceId
      Added value: +{
+  "description": "Only this subsequence of the campaign (id from list_subsequences); overrides `scope` (UUID).",
+  "format": "uuid",
+  "type": "string"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish that this is a safe read-only, idempotent operation, but the description adds meaningful behavioral detail: default inclusion of subsequences with each email and person counted once, optional breakdown tables, and optional time-series output. These aggregation semantics go beyond the safety profile and help the agent understand how results are computed.

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 front-loaded with the core metric list, then proceeds to scoping, breakdown, and interval behavior in compact sentences. It is dense but efficient, with no wasted framing or repetition.

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?

For an eight-parameter analytics tool with no output schema, the description is quite complete: it names the metrics returned, explains default aggregation, and describes optional breakdown and time-series additions. It could be stronger if it clarified the response shape when breakdown and interval are combined, but overall it covers what the agent needs to call the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is high at 88%, so the baseline is 3, but the description adds useful meaning beyond the schema by explaining that breakdown produces per-mailbox, per-step/variant, or per-bounce-type tables. It also clarifies that subsequenceId narrows to one subsequence and overrides scope, though several of those details are already present in the schema.

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 that this returns campaign performance metrics for a period and enumerates the metrics included. It distinguishes campaign-level analytics from broader workspace analytics only implicitly, and does not directly name sibling tools like get_workspace_analytics or get_campaign.

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 how to adjust scope using the default family aggregation, `scope: "main"`, and `subsequenceId`, which gives useful conditional guidance. However, it does not explicitly say when to choose this tool over `get_campaign` or `get_workspace_analytics`, so the usage guidance remains implied rather than explicit.

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

All MailBeast.ai toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources