Skip to main content
Glama
wuapidev

wuapi MCP server

Official
by wuapidev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get a message

get_message
Read-onlyIdempotent

Retrieve a WhatsApp message by ID to view its status, content, and any error. Optionally download its media and get a direct URL that requires no API key.

Instructions

One message with its status (queued, sent, delivered, read, failed, or received for inbound), content, and error when it failed. Received media is on demand by default (media.downloaded: false): pass fetchMedia: true to download it once and get a direct mediaFile.url that needs no API key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageIdYesA wuapi message id (from list_messages, a send tool, or a webhook).
fetchMediaNoAlso download the message's media if needed and return its direct URL as `mediaFile`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • addedInput schema / properties / fetchMedia
      Added value: +{
+  "description": "Also download the message's media if needed and return its direct URL as `mediaFile`.",
+  "type": "boolean"
+}
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: it lists possible status values, explains that failed messages include an error, and describes the media download default and the direct URL behavior. It does not cover auth requirements or error cases beyond status='failed'.

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?

The description is two sentences, front-loaded with the core return information and then the media behavior. Every sentence adds useful detail without redundancy.

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?

With no output schema, the description carries the burden of explaining return values, and it does so by naming statuses, content, error, and mediaFile. Annotations cover the read-only safety profile. It is nearly complete, though it omits not-found or auth error behavior.

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 description coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema for fetchMedia by saying it downloads media once and returns a direct mediaFile.url that needs no API key. It adds little for messageId beyond what the schema already states.

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 clearly states that this returns a single message with its status, content, error, and media details. The singular 'One message' distinguishes it from list_messages, but it does not explicitly name or contrast with any sibling tool. This is clear but lacks explicit sibling differentiation.

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?

The description gives no guidance on when to use get_message instead of list_messages or other retrieval tools. It explains the media fetch behavior but does not provide usage context or alternatives. An agent must infer when this tool is appropriate.

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