Skip to main content
Glama
WhatsApp MCP Server

WhatsApp MCP Server

draft_message

Pre-fills a WhatsApp conversation with the recipient and message text without sending it, so users can review, edit, or manually send after confirming with biometric verification.

Instructions

Open WhatsApp with the recipient focused and message body pre-filled without pressing Enter. Allows the user to review, edit, or manually send the message in the app. Requires explicit user confirmation (confirm=true) and native biometric verification.

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": {
      "recipient": "<recipient>",
      "text": "<text>"
    },
    "name": "draft_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesMessage content to pre-fill in the conversation.
confirmNoExplicit confirmation to execute this operation. Must be set to true.
recipientYesTarget phone number or WhatsApp JID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses the key behavior: it opens WhatsApp, focuses the recipient, pre-fills the body, does not press Enter, and requires confirm=true plus biometric verification. It does not describe failure behavior or what the agent receives after invocation, which is a notable but not severe gap.

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?

The description is three compact sentences with the primary action front-loaded. Every sentence adds relevant information about behavior, user control, or required confirmation.

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 native app interaction with no output schema and no annotations, the description covers the essential side effect, user-review flow, and confirmation/auth requirements. It could be more complete by explaining post-invocation results or error handling, but the core information needed to invoke it correctly is present.

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%, so the input schema already documents recipient, text, and confirm. The description adds useful context about pre-filling and focusing, but the confirm=true requirement largely repeats the schema description, so this is a baseline-level contribution.

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?

The description states a specific action and resource: opening WhatsApp with the recipient focused and the message body pre-filled without pressing Enter. It clearly distinguishes drafting from sending by emphasizing that the user can review, edit, or manually send the message.

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?

The description gives clear context for when this tool is appropriate: when a message should be prepared for review rather than sent immediately. It also states that explicit confirmation and native biometric verification are required, though it does not explicitly name alternative tools such as send_message.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.