Skip to main content
Glama
wazap-mcp

wazap-mcp

by razvangirgiz

Draft a WhatsApp message

send_message

Draft WhatsApp text, media, polls, locations, or forwards from a chat and content, returning a preview and draft_id for confirmation before anything is sent.

Instructions

Drafts text, media, polls, locations, forwards; sends nothing. Call it as soon as you have recipient and text: it returns draft_id and preview (recipient, number, exact text). Show that preview; confirm_send only on a yes to this text and recipient — a send in the same request is that yes.

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": {
      "chat_id": "<chat_id>",
      "text": "<text>"
    },
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
asNoMedia: send as a document, voice note or GIF
urlNoMedia: public http(s) URL
mimeNo
textYesThe message, or caption, poll question, place name; "" for a forward, voice note or audio
addressNoLocation: shown under the name
chat_idYesChat id, or a phone number
forwardNoForward this message; text ""
optionsNoPoll answers
send_atNoSend later: "2026-10-12T09:00" in time_zone, or with an offset
filenameNoWith data_base64
latitudeNo
reply_toNo
file_pathNoMedia: a path on wazap's machine
longitudeNo
time_zoneNoIANA zone for send_at; the server's by default
account_idNo
data_base64NoMedia: the file, base64, ≤5 MB
mention_idsNoChat ids to @-mention; write @<number> in text for each
multi_selectNoPoll: several answers allowed

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv1.7.4
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / as / description
      Previous value: -"Media: a plain document, a voice note, a looping GIF"New value: +"Media: send as a document, voice note or GIF"
    • addedInput schema / properties / data_base64
      Added value: +{
      +  "description": "Media: the file, base64, ≤5 MB",
      +  "type": "string"
      +}
    • changedInput schema / properties / file_path / description
      Previous value: -"Media: absolute path on the machine running wazap"New value: +"Media: a path on wazap's machine"
    • addedInput schema / properties / filename
      Added value: +{
      +  "description": "With data_base64",
      +  "type": "string"
      +}
    • removedInput schema / properties / forward / $ref
      Removed value: -"#/properties/reply_to"
    • addedInput schema / properties / forward / minLength
      Added value: +5
    • addedInput schema / properties / forward / type
      Added value: +"string"
    • addedInput schema / properties / mime
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / properties / send_at / description
      Previous value: -"Send later: \"2026-10-12T09:00\" in time_zone, or with an offset; 1 minute to 365 days ahead"New value: +"Send later: \"2026-10-12T09:00\" in time_zone, or with an offset"
    • changedInput schema / properties / text / description
      Previous value: -"The message, or the caption, poll question or place name; \"\" for a forward, a voice note or audio"New value: +"The message, or caption, poll question, place name; \"\" for a forward, voice note or audio"
    • changedInput schema / properties / time_zone / description
      Previous value: -"IANA zone for send_at, e.g. \"Europe/Bucharest\"; the server's by default"New value: +"IANA zone for send_at; the server's by default"
  2. Changed1 schema field changedv1.6.0
    • removedInput schema / properties / account_id / description
      Removed value: -"Account id"
  3. Changed2 schema fields changedv1.4.0
    • addedInput schema / properties / send_at
      Added value: +{
      +  "description": "Send later: \"2026-10-12T09:00\" in time_zone, or with an offset; 1 minute to 365 days ahead",
      +  "maxLength": 40,
      +  "minLength": 10,
      +  "type": "string"
      +}
    • addedInput schema / properties / time_zone
      Added value: +{
      +  "description": "IANA zone for send_at, e.g. \"Europe/Bucharest\"; the server's by default",
      +  "maxLength": 64,
      +  "minLength": 1,
      +  "type": "string"
      +}
  4. Changed15 schema fields changedv1.0.3
    • changedInput schema / properties / account_id / description
      Previous value: -"Registry account id (default, work, …). Omit to resolve from chat_id or message_id, or the default account."New value: +"Account id"
    • addedInput schema / properties / address
      Added value: +{
      +  "description": "Location: shown under the name",
      +  "maxLength": 500,
      +  "type": "string"
      +}
    • addedInput schema / properties / as
      Added value: +{
      +  "description": "Media: a plain document, a voice note, a looping GIF",
      +  "enum": [
      +    "document",
      +    "voice",
      +    "gif"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / chat_id / description
      Previous value: -"Chat id as returned by another tool (\"<digits>@s.whatsapp.net\" or \"<id>@g.us\"), or a phone number in international format"New value: +"Chat id, or a phone number"
    • addedInput schema / properties / file_path
      Added value: +{
      +  "description": "Media: absolute path on the machine running wazap",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / forward
      Added value: +{
      +  "$ref": "#/properties/reply_to",
      +  "description": "Forward this message; text \"\""
      +}
    • addedInput schema / properties / latitude
      Added value: +{
      +  "maximum": 90,
      +  "minimum": -90,
      +  "type": "number"
      +}
    • addedInput schema / properties / longitude
      Added value: +{
      +  "maximum": 180,
      +  "minimum": -180,
      +  "type": "number"
      +}
    • changedInput schema / properties / mention_ids / description
      Previous value: -"Chat ids to @-mention; write @<number> in the text for each, or wazap adds it at the end"New value: +"Chat ids to @-mention; write @<number> in text for each"
    • addedInput schema / properties / multi_select
      Added value: +{
      +  "description": "Poll: several answers allowed",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / options
      Added value: +{
      +  "description": "Poll answers",
      +  "items": {
      +    "maxLength": 100,
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  "maxItems": 12,
      +  "minItems": 2,
      +  "type": "array"
      +}
    • removedInput schema / properties / reply_to / description
      Removed value: -"Quote-reply to this message"
    • changedInput schema / properties / text / description
      Previous value: -"The message text"New value: +"The message, or the caption, poll question or place name; \"\" for a forward, a voice note or audio"
    • removedInput schema / properties / text / minLength
      Removed value: -1
    • addedInput schema / properties / url
      Added value: +{
      +  "description": "Media: public http(s) URL",
      +  "format": "uri",
      +  "type": "string"
      +}
  5. Changed1 schema field changedv0.21.0
    • changedInput schema / properties / mention_ids / description
      Previous value: -"Chat ids to @-mention; include their names in the text yourself"New value: +"Chat ids to @-mention; write @<number> in the text for each, or wazap adds it at the end"
  6. Changed1 schema field changedv0.15.0
    • addedInput schema / properties / account_id
      Added value: +{
      +  "description": "Registry account id (default, work, …). Omit to resolve from chat_id or message_id, or the default account.",
      +  "minLength": 1,
      +  "type": "string"
      +}
  7. First observedv0.9.3

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description adds the crucial nuance that despite being a write, nothing leaves the system until confirm_send. It also pre-empts the missing output schema by naming the return shape (draft_id, preview with recipient, number, exact text). It does not discuss idempotency or what happens when a draft is never confirmed, which keeps it short of a 5.

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 sentences, front-loaded with capability and the non-sending guarantee, then the workflow. Dense but every clause carries information; the second sentence is a long chain of clauses that could be split for readability but no content is wasted.

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 19-parameter tool with no output schema, the description covers the two things an agent most needs that structured fields cannot convey: the side-effect boundary and the return shape. Parameter-level detail is delegated to a 74%-covered schema, which is a reasonable division, though scheduling and mention parameters get no narrative support.

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?

The schema documents 74% of 19 parameters itself, so the baseline is 3. The description's enumeration of message types (text, media, polls, locations, forwards) maps loosely onto the parameter groups and its mention of 'recipient and text' flags the two required fields, but it adds no per-parameter meaning such as the forward-plus-empty-text convention or media source options.

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?

'Drafts text, media, polls, locations, forwards; sends nothing' gives a specific verb plus the full resource scope, and the 'sends nothing' clause immediately separates it from confirm_send and from any real send path among the siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the precise trigger ('Call it as soon as you have recipient and text') and names the exact alternative plus the condition that selects it ('Show that preview; confirm_send only on a yes to this text and recipient'). No inference about the draft/confirm split is left to the agent.

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