Skip to main content
Glama
razvangirgiz

wazap-mcp

by razvangirgiz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get one WhatsApp message in full

get_message
Read-onlyIdempotent

Retrieve a complete WhatsApp message by message_id, including quoted reply, reactions, and media metadata, to provide context for a message found via search or read.

Instructions

The complete message behind a message_id, including the quoted message it replies to, its reactions, and its media metadata. Use it after search_messages or read_messages when you need the context around a single message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idNoRegistry account id (default, work, …). Omit to resolve from chat_id or message_id, or the default account.
message_idYesMessage id from read_messages / search_messages / get_message, e.g. "false_4072...@s.whatsapp.net_3EB0..."

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. First observedv0.9.3

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so the safety profile is covered. The description adds value beyond that by disclosing the return content shape (quoted message, reactions, media metadata), which matters because there is no output schema. It does not cover error behavior for an unknown message_id, keeping it below 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, and the payload content is front-loaded before the routing advice. Every clause earns its place.

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 2-param read tool with no output schema, the description supplies the missing return-content detail (quoted message, reactions, media metadata) plus entry-point guidance. Failure modes (unknown or inaccessible message_id) are not mentioned, so it is not fully complete.

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 description coverage is 100%, so both account_id (fallback resolution rules) and message_id (format example) are already fully documented in the schema. The description adds no parameter meaning beyond that, which is the baseline 3 case when the schema does the heavy lifting.

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 ('The complete message behind a message_id') and immediately enumerates what 'complete' means: quoted message, reactions, media metadata. An agent can distinguish it from read_messages and search_messages without opening any 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?

Explicitly says to use it 'after search_messages or read_messages when you need the context around a single message', naming the sibling tools that precede it. It stops short of stating when *not* to use it (e.g. bulk retrieval should use read_messages), so it is clear context without exclusions.

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