Skip to main content
Glama

WhatsMCP: MCP for WhatsApp

by com.whatsmcp.app
OverviewDiscussionsAdmin

Get Message

wa_get_message
Read-only

Fetch ONE stored message from one of your accounts, by WhatsApp's message_id (as a webhook delivery or wa_list_messages gave it) or by its cursor. Use this to read the message a webhook told you about, or the one you are about to react to, edit or delete, without paging through history.

Input Schema

NameRequiredDescriptionDefault
cursorNothe message's cursor, as wa_list_messages returned it (a webhook delivery carries it as message_seq). Pass this or message_id
account_idNothe account the message belongs to, from wa_list_accounts; omit it when the workspace has only one account
message_idNoWhatsApp's id for the message — the message_id a webhook delivery, wa_list_messages or wa_send_message gave you. Pass this or cursor
include_media_urlsNoalso return attachment.media_url when the message carries an available attachment — a time-limited (1h) signed URL to GET the bytes with plain HTTP instead of a wa_get_media call; off by default

Output Schema

NameRequiredDescriptionDefault
messageNothe message; absent when the request was declined
refusalNopresent only when the request was declined — including when no such message is stored
account_noticesNopresent when a number this read covers is not working: new messages are not arriving on it; says why and what to do

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / account_id / description
      Previous value: -"the account the message belongs to, from wa_list_accounts"New value: +"the account the message belongs to, from wa_list_accounts; omit it when the workspace has only one account"
    • addedInput schema / properties / include_media_urls
      Added value: +{
+  "description": "also return attachment.media_url when the message carries an available attachment — a time-limited (1h) signed URL to GET the bytes with plain HTTP instead of a wa_get_media call; off by default",
+  "type": "boolean"
+}
    • removedInput schema / required
      Removed value: -[
-  "account_id"
-]
    • changedOutput schema / properties / message / properties / attachment / description
      Previous value: -"present on an image, video, audio, document or sticker message: the file's mime type, size and name; fetch the bytes with wa_get_media"New value: +"present on an image, video, audio, document or sticker message: the file's mime type, size and name; fetch the bytes with wa_get_media, or pass include_media_urls on the read to get a direct media_url"
    • addedOutput schema / properties / message / properties / attachment / properties / media_url
      Added value: +{
+  "description": "a time-limited (1h) signed URL to GET the attachment's bytes, present only when the read passed include_media_urls and the attachment is available; an expired link is refused — read again for a fresh one",
+  "type": "string"
+}
    • addedOutput schema / properties / refusal / properties / candidates
      Added value: +{
+  "description": "on an account_ambiguous refusal: the accounts to choose from — retry with one of these as account_id",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "account_id": {
+        "description": "the id to retry with as account_id",
+        "type": "string"
+      },
+      "name": {
+        "description": "the account's WhatsApp display name",
+        "type": "string"
+      },
+      "phone": {
+        "description": "the account's phone number, E.164",
+        "type": "string"
+      },
+      "status": {
+        "description": "whether the number works right now — live, connecting, or why not, as wa_list_accounts reports it",
+        "type": "string"
+      }
+    },
+    "required": [
+      "account_id"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}
  2. Changed2 schema fields changed
    • changedOutput schema / properties / message / properties / chat / description
      Previous value: -"the conversation JID; pass it to wa_send_message's 'to' to reply here — a group is …@g.us, a channel …@newsletter"New value: +"the conversation JID; pass it to wa_send_message's 'to' to reply here — a group is …@g.us, a channel …@newsletter; on a Telegram account a Telegram id: <id>@telegram for a user, -<id>@telegram for a basic group, -100<id>@telegram for a channel or supergroup"
    • changedOutput schema / properties / message / properties / peer / description
      Previous value: -"the other party's phone number (for a group/channel this is the individual SENDER; use chat to reply)"New value: +"the other party's phone number (for a group/channel this is the individual SENDER; use chat to reply); on a Telegram account the other party's Telegram id, <id>@telegram"
  3. Changed1 schema field changed
    • changedOutput schema / properties / message / properties / kind / description
      Previous value: -"what the message is: text, image, video, audio, document, sticker, reaction, location, live_location, contact, poll, poll_vote, video_note, album, event, comment, pin, group_invite or template; other is a type this server does not classify. text carries a body, and so do image/video/document captions and template text; an image, video, audio, document or sticker attachment can be fetched with wa_get_media"New value: +"what the message is: text, image, video, audio, document, sticker, reaction, location, live_location, contact, poll, poll_vote, video_note, album, event, comment, pin, group_invite, template or call_permission; other is a type this server does not classify. text carries a body, and so do image/video/document captions, template text and a call_permission request or answer; an image, video, audio, document or sticker attachment can be fetched with wa_get_media"
  4. Changed4 schema fields changed
    • addedOutput schema / properties / account_notices
      Added value: +{
+  "description": "present when a number this read covers is not working: new messages are not arriving on it; says why and what to do",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "account_id": {
+        "description": "the account this notice is about",
+        "type": "string"
+      },
+      "message": {
+        "description": "what is wrong and what to do; tell the user",
+        "type": "string"
+      },
+      "since": {
+        "description": "when it stopped working, RFC3339, when known",
+        "type": "string"
+      },
+      "status": {
+        "description": "why it is not live: starting, not_running, whatsapp_down, suspended, pairing, unlinked or locked",
+        "type": "string"
+      },
+      "status_reason": {
+        "description": "the detail, e.g. no_egress, no_plan, stopped",
+        "type": "string"
+      }
+    },
+    "required": [
+      "account_id",
+      "status",
+      "message"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}
    • addedOutput schema / properties / refusal / properties / account_status
      Added value: +{
+  "description": "when the number is not working: its status — starting, not_running, whatsapp_down, suspended, pairing, unlinked or locked",
+  "type": "string"
+}
    • addedOutput schema / properties / refusal / properties / account_status_reason
      Added value: +{
+  "description": "the detail of account_status, e.g. no_egress, stopped, no_plan",
+  "type": "string"
+}
    • addedOutput schema / properties / refusal / properties / since
      Added value: +{
+  "description": "when the number stopped working, RFC3339, when known",
+  "type": "string"
+}
  5. Changed5 schema fields changed
    • addedOutput schema / properties / message / properties / account_name
      Added value: +{
+  "description": "the WhatsApp display name of that account",
+  "type": "string"
+}
    • addedOutput schema / properties / message / properties / account_phone
      Added value: +{
+  "description": "the phone number of your account this message was sent from or received on, E.164",
+  "type": "string"
+}
    • addedOutput schema / properties / message / properties / attachment
      Added value: +{
+  "additionalProperties": false,
+  "description": "present on an image, video, audio, document or sticker message: the file's mime type, size and name; fetch the bytes with wa_get_media",
+  "properties": {
+    "available": {
+      "description": "true when the file should be fetchable with wa_get_media(account_id, message_id) — a live received attachment; false for history and for files you sent, which are not kept",
+      "type": "boolean"
+    },
+    "file_name": {
+      "description": "documents only: the file name the sender gave it",
+      "type": "string"
+    },
+    "mime": {
+      "description": "the attachment's mime type as the sender declared it, e.g. image/jpeg or application/pdf; empty for a message stored before this was recorded",
+      "type": "string"
+    },
+    "size": {
+      "description": "the attachment's size in bytes as the sender declared it; 0 when unknown",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "available"
+  ],
+  "type": [
+    "null",
+    "object"
+  ]
+}
    • addedOutput schema / properties / message / properties / received_at
      Added value: +{
+  "description": "when this server received and stored the message, RFC3339; later than at for a message delivered late or loaded as history",
+  "type": "string"
+}
    • addedOutput schema / properties / message / properties / sender_name
      Added value: +{
+  "description": "who wrote the message, by name: for inbound the sender's name as saved in this account's contacts, or else the name they chose for themselves; for outbound this account's own WhatsApp name. Empty when no name is known",
+  "type": "string"
+}
  6. Changed1 schema field changed
    • addedOutput schema / properties / message / properties / status
      Added value: +{
+  "description": "delivery status of an outbound message from the provider's receipts: sent, delivered, read or failed; empty when no receipt has arrived (or for inbound). Only Business (Cloud API) numbers report this today",
+  "type": "string"
+}
  7. Changed1 schema field changed
    • addedOutput schema / properties / message / properties / imported
      Added value: +{
+  "description": "true for a message loaded as history (pairing sync or wa_load_history) rather than received live",
+  "type": "boolean"
+}
  8. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces the non-mutating single-record read while adding that the caller avoids paging. It also points out that media bytes are normally fetched separately, though it does not state what happens when neither cursor nor message_id resolves.

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?

One sentence for the what and keys, a second for the when, front-loaded with no filler. Every clause carries information an agent can act on.

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?

With a full output schema and fully described parameters, the description only needs to justify the lookup path and the intended use, both of which it covers. Nothing an agent needs in order to call it correctly is missing.

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% and the schema already documents cursor vs message_id and the 1h signed media URL. The description only echoes that message_id comes from a webhook or wa_list_messages and adds no format or precedence detail beyond the parameter definitions, so baseline 3 applies.

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 ('Fetch ONE stored message') and names the exact lookup keys (message_id or cursor). The capitalized 'ONE' plus 'without paging through history' separates it cleanly from wa_list_messages.

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 concrete triggers: read the message a webhook told you about, or the one you are about to react to, edit or delete. It implies history browsing belongs to wa_list_messages rather than naming it as the alternative with an explicit exclusion, so the routing guidance is clear but not fully spelled out.

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

All WhatsMCP: MCP for WhatsApp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources