Skip to main content
Glama

prepare_email_campaign_review

Prepare a saved campaign and its eligible audience for owner confirmation in Cockatoo. Choose either a segment or contact IDs. Optionally propose a send time within the next 30 days as Unix milliseconds.

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>",
      "campaignRevision": "<campaignRevision>",
      "settingsRevision": "<settingsRevision>"
    },
    "name": "prepare_email_campaign_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
audienceNo
campaignIdYes
contactIdsNo
scheduledAtNo
campaignRevisionYes
settingsRevisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, non-idempotent operation, so the main disclosure burden is lifted. The description adds useful context that this persists a pending item awaiting owner confirmation rather than sending immediately, and that proposed send times are limited to 30 days, but says nothing about side effects, permissions, or effects on the saved draft.

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?

Three short sentences, front-loaded with the action and followed by the parameter choice and the optional scheduling constraint. No filler or restated title text; every sentence carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter tool with zero schema description coverage, no output schema, and three required revision fields, the description covers the audience and scheduling semantics adequately but omits what the revision parameters mean and how conflicts are handled. An agent could call it, but could easily mis-handle concurrency token semantics.

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 0%, so the description must carry the load, and it does add real meaning for two parameters: the audience-versus-contactIds exclusivity (not encoded in the schema's oneOf, which only covers audience kinds) and scheduledAt's Unix-millisecond format plus a 30-day ceiling absent from the schema. The three required revision parameters (campaignRevision, settingsRevision) are left entirely unexplained, which is a material gap.

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?

States a specific verb and resource ('Prepare a saved campaign and its eligible audience for owner confirmation') and scopes it to a workflow stage, which distinguishes it from siblings like save_email_campaign_draft and preview_email_audience. It stops short of naming an alternative tool explicitly, so an agent must infer the boundary from context.

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 phrase 'for owner confirmation' implies this is the pre-confirmation step in a campaign workflow, and 'Choose either a segment or contact IDs' gives a selection rule. However, there is no explicit when-to-use/when-not guidance and no sibling alternative named, leaving routing to inference.

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