Skip to main content
Glama

Create a WhatsApp campaign (draft)

campaign_create

Creates a WhatsApp campaign as a DRAFT for a list of recipients; nothing is sent. Needs the id of an APPROVED template. Up to 1000 recipients, each with optional per-recipient variables.

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": {
      "name": "<name>",
      "templateId": "<templateId>",
      "recipients": "<recipients>"
    },
    "name": "campaign_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesCampaign name
dryRunNoIf true, validate and return the payload without creating
sendRateNoMessages per minute, default 10
recipientsYes
templateIdYesAn APPROVED template's id
descriptionNo
phoneNumberIdNoWhich of the organisation's WhatsApp numbers sends it; default the primary
suppressRecentDaysNoSkip anybody messaged within this many days

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / templateId / description
      Previous value: -"An APPROVED template's template_id, from template_list"New value: +"An APPROVED template's id"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare the generic mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false); the description adds the important behavioral fact that the result is a non-sending draft and that the template must already be approved. It does not mention what happens on repeated calls (duplicate drafts) or that validation can be done without creating, both of which an agent would want to know.

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?

Two tight sentences, with the draft/no-send constraint front-loaded where an agent will see it first. No filler and no repetition across sentences.

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 8-parameter, non-destructive creation tool with no output schema, the description covers the essentials: what is produced (a draft), the hard prerequisite (approved template), and the recipient bound. The remaining gaps (rate limiting, suppression window, dry-run) are adequately documented in the schema descriptions.

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 coverage is 75%, so the baseline is 3. The description's parameter content largely restates the schema (approved template id, 1000-recipient cap, optional per-recipient variables) and leaves sendRate, suppressRecentDays, phoneNumberId and dryRun to the schema, so it adds little meaning beyond structured fields.

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 opens with a specific verb and resource ("Creates a WhatsApp campaign") and immediately qualifies the output as a DRAFT, which distinguishes it conceptually from a launch operation. It stops short of naming a sibling such as campaign_launch, so the differentiation is implied rather than explicit.

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?

It supplies a real prerequisite ("Needs the id of an APPROVED template") and clarifies that nothing is sent, which implies this is the staging step before sending. However, there is no explicit when-to-use/when-not guidance and no named alternative for actually dispatching the campaign.

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.