Skip to main content
Glama
wsapi-chat

WSAPI WhatsApp MCP Server

by wsapi-chat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

whatsapp_send_text

Send a text message to a WhatsApp user or group JID, supporting mentions, replies, and disappearing timers. Returns the message ID.

Instructions

Send a text message to a user JID or a group JID (@g.us). The recipient receives it immediately and it cannot be unsent, only deleted with whatsapp_delete_message. Supports mentions, replies and a disappearing timer. Not idempotent: calling it twice sends two messages. Returns the message ID.

Input Schema

NameRequiredDescriptionDefault
toYesRecipient JID (user or group)
textYesMessage text content (max 4096 characters)
replyToNoID of the message being replied to
mentionsNoJIDs of mentioned users
isForwardedNoMark as forwarded
replyToSenderIdNoSender JID of the message being replied to
ephemeralExpirationNoDisappearing message timer

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv2.0.0
    • addedInput schema / properties / ephemeralExpiration
      Added value: +{
+  "description": "Disappearing message timer",
+  "enum": [
+    "off",
+    "24h",
+    "7d",
+    "90d"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / isForwarded / description
      Previous value: -"Whether the message should be marked as forwarded"New value: +"Mark as forwarded"
    • removedInput schema / properties / isForwarded / optional
      Removed value: -true
    • changedInput schema / properties / mentions / description
      Previous value: -"List of phone numbers to mention in the message"New value: +"JIDs of mentioned users"
    • removedInput schema / properties / mentions / optional
      Removed value: -true
    • removedInput schema / properties / replyTo / optional
      Removed value: -true
    • addedInput schema / properties / replyToSenderId
      Added value: +{
+  "description": "Sender JID of the message being replied to",
+  "type": "string"
+}
    • changedInput schema / properties / to / description
      Previous value: -"Recipient phone number (with @s.whatsapp.net) or group ID (with @g.us)"New value: +"Recipient JID (user or group)"
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly=false, idempotent=false, destructive=false and openWorld=true, yet the description still adds real value: irreversibility, the concrete alternative for removal, and the fact that duplicate calls produce duplicate messages. It also notes the return value (message ID) despite the absence of an output schema.

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?

Four tight sentences with no filler, leading with the core action and recipient formats before consequences. The idempotency sentence slightly repeats the annotations, keeping it out of 5 territory.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter mutation tool with full schema coverage, no output schema and useful annotations, the description covers purpose, side effects, reversibility, and return value. Nothing needed to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so the baseline is 3, but the description adds the group JID format suffix (<id>@g.us) that the schema only gestures at with 'user or group', and it surfaces the mentions/replies/disappearing-timer capabilities that map onto optional parameters.

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 ('Send a text message') plus the accepted recipient forms, and implicitly distinguishes itself from the sibling senders (send_audio, send_image, send_document). An agent can route to it without opening the 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?

Gives clear operating context — the message is delivered immediately, cannot be unsent, and can only be removed via whatsapp_delete_message, with an explicit idempotency warning. It stops short of stating when to prefer it over e.g. send_link or a reaction, so no explicit exclusions/alternatives beyond deletion.

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

Deploy Server

Other Tools