Skip to main content
Glama

whatsapp_campaigns_read

Read-onlyIdempotent

List WhatsApp broadcast campaigns of an agent (template messages sent to a lead group) with sent / delivered / failed counts. Outbound CALL campaigns are in campaigns_read. Actions: list — paginated campaigns

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": {
      "action": "<action>",
      "agentId": "<agentId>"
    },
    "name": "whatsapp_campaigns_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNocompact (default) = light mode: long text is cut and bulky blobs are replaced by a size marker. full = complete API response.
pageNo
limitNoDefault 20, max 100.
actionYes
agentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world, so the safety profile is covered. The description adds that results are paginated and lists the aggregate counts returned, but says nothing about ordering, defaults applied, or what compact mode does at runtime (that lives only in the schema). Moderate added value, not rich.

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?

Two tight sentences, front-loaded with what is listed and what counts come back, followed by the sibling routing and the action list. The trailing 'Actions: list — paginated campaigns' is slightly telegraphic but earns its place by naming the only supported action.

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 usefully summarizes the return payload as sent/delivered/failed counts. Combined with annotations covering safety and the schema covering mode/limit, an agent has enough to call it correctly; only page/agentId semantics remain thin.

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 only 40%, with page, agentId, and action undocumented in the schema. The description compensates partially: it conveys that results are scoped to an agent (agentId) and that listing is paginated (page/limit). It does not explain page semantics or default behavior, so the gap is narrowed but not closed.

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?

States a specific verb and resource ('List WhatsApp broadcast campaigns of an agent'), clarifies what these campaigns are (template messages to a lead group), and names the metrics returned. It also explicitly excludes outbound CALL campaigns by routing them to campaigns_read, so an agent can tell it apart from that sibling without reading either schema.

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?

Explicitly states that CALL campaigns belong in campaigns_read, which is a real alternative routing rule. It also names the supported action ('list') and notes pagination. What's missing is a when-not rule beyond the CALL-campaign exclusion, and any prerequisite context for agentId.

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