Skip to main content
Glama

WarmInboxes Free MCP

Pre-send campaign audit

audit_campaign
Read-onlyIdempotent

Audit a cold email campaign before launch: the lead CSV and the sequence checked together for merge tags with no column or empty values, variable syntax the sequencer will not parse, role and disposable addresses, duplicates and too many contacts per company, plus a send forecast from the sending settings. Pass the CSV text and every step of the sequence.

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": {
      "csv": "<csv>",
      "sequence": "<sequence>"
    },
    "name": "audit_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvYesThe lead CSV as text, header row first.
inboxesNoSending inboxes. Defaults to 5.
perInboxNoCold sends per inbox per day. Defaults to 15, the planner's Google Workspace pace; use 8 for Microsoft 365 and 2 to 6 for Azure by tenant density. A new campaign starts at 5.
sequenceYesEvery step of the sequence, merge tags as written, e.g. {{first_name}}.
daysPerWeekNoSending days a week. Defaults to 5.
stepGapDaysNoDays between steps. Defaults to 3.
maxPerCompanyNoContacts allowed per company domain. Defaults to 2.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / perInbox / description
      Previous value: -"Sends per inbox per day. Defaults to 30."New value: +"Cold sends per inbox per day. Defaults to 15, the planner's Google Workspace pace; use 8 for Microsoft 365 and 2 to 6 for Azure by tenant density. A new campaign starts at 5."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine behavioral context beyond that: it discloses the scope of the inspection (cross-checking CSV against sequence) and that a send forecast is derived from sending settings, making clear the result is a diagnostic report rather than a mutation. It does not describe the report's structure or whether issues are blocking vs. advisory.

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?

One front-loaded sentence carries the purpose and the full check list, followed by a short imperative on inputs. The check enumeration is long but each item earns its place by telling the agent what will be validated. Slight density cost, but no filler 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?

With no output schema, the description does well by naming the categories of findings and the forecast so the agent knows what comes back. Seven parameters are all schema-documented. The remaining gap is that result shape and severity/blocking semantics of findings are unspecified, which matters for a pre-launch gate tool.

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% and the parameter descriptions are already rich (defaults, provider-specific guidance for perInbox, enum for daysPerWeek), so the baseline is 3. The description's only added meaning is that sending settings feed the send forecast, and it reinforces that 'sequence' means every step with merge tags as written; it adds little the schema does not already say.

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?

Opens with a specific verb and resource ('Audit a cold email campaign before launch') and then enumerates the exact checks performed: merge tags vs. columns/empty values, variable syntax, role/disposable addresses, duplicates, per-company caps, and a send forecast. This clearly separates it from siblings like clean_csv, plan_from_list, or check_deliverability, which either fix data or test infrastructure rather than auditing a campaign bundle.

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?

The timing guidance is explicit ('before launch'), and the final sentence tells the caller exactly what to supply ('Pass the CSV text and every step of the sequence'), which is the key invocation precondition. It stops short of naming alternatives or exclusions, e.g. that clean_csv should be run first to repair a broken CSV or that verify_email handles single-lead checks.

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