Skip to main content
Glama

Get one WhatsApp campaign

campaign_detail
Read-onlyIdempotent

Everything stored about one campaign: template, status, schedule, and per-recipient counts. Takes a campaign id.

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>"
    },
    "name": "campaign_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaignIdYesThe campaign's id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / campaignId / description
      Previous value: -"Campaign id, as returned by campaign_list"New value: +"The campaign'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 already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds value by enumerating what the response contains (template, status, schedule, per-recipient counts), which matters because no output schema exists. It stops short of noting cost, freshness, or what happens for an unknown id.

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 short sentences with zero filler, and the payload contents are front-loaded before the parameter note. Every clause contributes information.

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 a one-parameter read tool with full annotation coverage and no output schema, the description supplies the missing return-content summary, which is the main gap it needed to fill. Only minor items like behavior on an invalid or unknown campaign id are absent.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents it fully. 'Takes a campaign id' adds nothing beyond that, which is the expected baseline when the schema carries the burden.

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 states a specific resource and scope: 'Everything stored about one campaign: template, status, schedule, and per-recipient counts.' An agent can tell this is a single-record fetch rather than a list or mutation. It does not explicitly distinguish itself from campaign_list or campaign_insights, but the singular 'one campaign' framing makes the distinction inferable.

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 'Takes a campaign id' — call it when you already have an id and want the full record. There is no explicit statement of when to prefer this over campaign_list or campaign_insights, and no exclusions or prerequisites beyond the required id.

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.