Skip to main content
Glama

Get WhatsApp campaign

get_whatsapp_campaign
Read-onlyIdempotent

Get one WhatsApp campaign with its progress: stats counts recipients by status (queued, sending, sent, delivered, read, failed, and skipped_* for contacts deliberately not messaged: opted out, Meta frequency cap, missing variable, region restricted, no WhatsApp identity), plus its send window, pace and daily cap. failure_reason says why a failed campaign stopped; paused_until is a cooldown Meta asked for. replies_count is how many recipients replied; lead_stats counts their replies by lead stage: hot and warm are qualified, cold, needs_review (a person should look), opted_out, unscored (not assessed). Empty when reply qualification is off. Spanish names of the stages: caliente, tibio, frío, por revisar, dado de baja, sin calificar.

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": {
      "campaign_id": "<campaign_id>"
    },
    "name": "get_whatsapp_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoOptional: return only these fields of each record.
campaign_idYesCampaign id as returned by list_whatsapp_campaigns.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the description is free to add domain behavior — and it does: what stats counts, which skipped_* categories mean a contact was deliberately not messaged, what failure_reason and paused_until signify, and that lead_stats is empty when reply qualification is off. This is genuinely load-bearing context an agent could not get from the annotations.

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?

The purpose clause is front-loaded and nearly every sentence carries information about a returned field. It is a single dense paragraph, though, with the status taxonomy and the Spanish stage aliases packed inline, which makes it harder to scan than a lightly structured version would be.

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 return-value burden and does so thoroughly for the non-obvious fields (stats, skipped_*, failure_reason, paused_until, replies_count, lead_stats). Gaps are minor: plain fields like name/status/schedule are left to the schema, and error behavior for an invalid campaign_id is unaddressed.

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 100%, with campaign_id documented as 'as returned by list_whatsapp_campaigns' and fields described in-schema, so the baseline of 3 applies. The description adds no meaning about the fields projection parameter or its interaction with the stats/lead_stats content it spends so long explaining.

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+resource+scope: 'Get one WhatsApp campaign with its progress,' which clearly distinguishes the singular fetch from list-style siblings. It does not, however, name any sibling or state the boundary against list_whatsapp_campaigns, so the differentiation is only implicit.

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?

Usage is implied by 'Get one ... campaign' plus the required campaign_id, which is enough to infer this is the single-record lookup. There is no explicit statement of when to prefer it over list_whatsapp_campaigns, list_whatsapp_campaign_recipients, or get_campaign, and no exclusions or prerequisites are given.

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