Skip to main content
Glama

Turbo Notify: WhatsApp for AI agents

Get one message in full

get_message
Read-onlyIdempotent

Fetch one WhatsApp message with its full content, parties and mentions.

The answer includes the number's stable number_id (num_…) next to number_alias.

at is when the message actually happened on WhatsApp; status.at is when it reached its current delivery status and keeps moving as receipts arrive. They answer different questions and are not interchangeable.

Returns not found if the id belongs to a different number. Past the organization's content retention window (1 hour by default, up to 72 hours depending on the plan) the message is still returned, with content_expired true and its content empty.

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
message_idYesMessage id (`msg_…`), as returned by a send or by `list_messages`.
number_aliasNoWhich of the organization's WhatsApp numbers this acts on: `main`, the alias of an extra number, or the number's `id` (`num_…`), which stays the same when the alias is renamed. Call `list_numbers` to see them. Defaults to the main number.main

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Goes well beyond the readOnly/idempotent annotations, disclosing the cross-number not-found case, the retention window (1 hour default, up to 72 hours by plan), and the degraded-but-successful return with `content_expired` true and empty content. That edge-case behavior is exactly the kind of thing an agent cannot infer elsewhere. Only slight gap: no rate-limit or pagination-style context.

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?

Front-loads the core action, then uses short paragraphs for the id, timestamp and retention caveats, each earning its place. The `at` vs `status.at` paragraph explains return fields that an output schema already covers, so it is somewhat redundant rather than wasteful.

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?

Annotations cover the safety profile and an output schema exists, so the description need not explain returns. What remains open is the relationship to siblings like `get_message_status`, which the description does not address, leaving routing decisions to inference.

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 coverage is 100%, so the baseline is 3; the description adds that `number_alias` resolves alongside a stable `number_id`, which clarifies why an alias can be swapped for an id. `message_id` semantics stay entirely in the schema, so the added value is modest but real.

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 WhatsApp message with its full content, parties and mentions") and uses "one" / "in full" to separate it from status, reactions, receipts and list-style siblings. An agent can pick it without opening a schema.

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

Usage Guidelines3/5

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

Usage is implied by "full content" retrieval, and the not-found condition (id belonging to another number) gives a useful boundary. However, it never says when to prefer this over `get_message_status` or `list_messages`, nor any prerequisite for obtaining a `msg_…` id outside the schema.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.