Skip to main content
Glama
wazap-mcp

wazap-mcp

by razvangirgiz

Get one WhatsApp message in full

get_message
Read-onlyIdempotent

Retrieve a full WhatsApp message by ID, including quoted text, reactions, poll and event responses, media, plus delivery and read receipts for your own messages.

Instructions

One message in full, its words never cut: the message it quotes, each reaction with who left it, poll votes and event answers by person, its media, and on the user's own messages who it reached and who read it.

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": {
      "message_id": "<message_id>"
    },
    "name": "get_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNo
message_idYes

Output Schema

NameRequiredDescriptionDefault
textYes
chat_idYes
timestampYes
account_idYes
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.7.4
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedOutput schema / additionalProperties
      Previous value: -trueNew value: +{}
  2. Changed1 schema field changedv1.6.0
    • removedInput schema / properties / account_id / description
      Removed value: -"Account id"
  3. Changed3 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"
    • removedInput schema / properties / message_id / description
      Removed value: -"Message id from read_messages / search_messages / get_message, e.g. \"false_4072...@s.whatsapp.net_3EB0...\""
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": true,
      +  "properties": {
      +    "account_id": {
      +      "type": "string"
      +    },
      +    "chat_id": {
      +      "type": "string"
      +    },
      +    "message_id": {
      +      "type": "string"
      +    },
      +    "text": {
      +      "type": "string"
      +    },
      +    "timestamp": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "message_id",
      +    "chat_id",
      +    "text",
      +    "timestamp",
      +    "account_id"
      +  ],
      +  "type": "object"
      +}
  4. 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"
      +}
  5. First observedv0.9.3

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld, so the safety profile is covered. The description still adds real behavioral value by disclosing exactly what is returned, including that message text is never truncated ('words never cut') and that delivery/read-receipt data appears only for the user's own messages. It does not mention failures for missing messages or access limits, which keeps it below 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?

Everything is packed into a single dense sentence with no filler, and the core claim (full message, untruncated text) is front-loaded. The long comma-separated enumeration of contents makes it slightly run-on, but each listed element is informative rather than redundant.

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

Completeness3/5

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

An output schema exists, so return structure need not be restated, and the description usefully summarizes the rich payload and the self-message read-receipt caveat. However, for a two-parameter lookup it leaves both parameters unexplained and gives no routing guidance among the many sibling tools. It is adequate but with clear gaps.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the burden, but it never explains either parameter. message_id is weakly implied by 'one message', while account_id is entirely unaddressed despite being needed to scope the lookup. With two undocumented parameters, the definition does not compensate for the schema gap.

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 names a specific resource (one WhatsApp message) and enumerates its scope: quoted message, reactions with authors, poll votes, event answers, media, and delivery/read receipts. This makes it clearly distinguishable from siblings like get_media or read_messages. It lacks an explicit retrieval verb, relying on the title for that, which keeps it just short of a 5.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus alternatives such as read_messages or search, and no when-not guidance. The only conditional information is 'on the user's own messages', which describes output behavior rather than tool selection. An agent must infer that this is the deep-detail lookup for a single known message_id.

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