Skip to main content
Glama

Turbo Notify: WhatsApp for AI agents

Reply to a message in the same conversation

reply_to_message

Reply on WhatsApp to an EARLIER message, quoting it, without naming a recipient.

Use it to bring context into the conversation: when the conversation has moved on and your answer depends on something said a while ago (by the contact, by you or, in a group, by any participant). To answer the message you just received, do not use this tool: send a normal message with send_text and let the chat carry the context, as a person would.

The recipient is worked out from the original: an inbound message is answered to its sender, an outbound one to whoever received it, and a group message to the group.

The message must belong to the number named by number_alias; a message_id from a different number returns not found.

Like a person opening the chat, the number first appears online and its unread messages in that conversation are marked as read, then the reply is sent. Opening the conversation this way is automatic and uses no quota of its own.

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>",
      "text": "<text>"
    },
    "name": "reply_to_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe text of your reply, 1 to 4096 characters.
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
idempotency_keyNoAny printable ASCII text you choose, 1 to 255 characters, for example the id of the event you are answering. Reusing it for the same number suppresses a duplicate if you retry, but only for the same request: the same key with another recipient or another text is refused as idempotency_key_conflict and nothing is sent, so use a new key for each new message. Without it, retrying after a timeout may deliver the message twice, and the recipient sees both.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"Any printable ASCII text you choose, 1 to 255 characters, for example the id of the event you are answering. Reusing it for the same number suppresses a duplicate if you retry. Without it, retrying after a timeout may deliver the message twice, and the recipient sees both."New value: +"Any printable ASCII text you choose, 1 to 255 characters, for example the id of the event you are answering. Reusing it for the same number suppresses a duplicate if you retry, but only for the same request: the same key with another recipient or another text is refused as idempotency_key_conflict and nothing is sent, so use a new key for each new message. Without it, retrying after a timeout may deliver the message twice, and the recipient sees both."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and idempotentHint=false but say nothing about side effects; the description fills that gap by disclosing that the number goes online and unread messages in that conversation are marked read, and that this consumes no quota. It also surfaces a failure mode (message_id from a different number returns not found) and retry/duplicate-delivery behavior. Slightly short of 5 only because the online/read-marking side effects are stated without noting whether they can be suppressed.

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-loaded with the core action and the when-not-to-use warning, then structured into short paragraphs covering recipient derivation, number scoping, and side effects. Some phrasing is leisurely ('Like a person opening the chat…'), but each sentence carries distinct information.

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?

For a 4-parameter, open-world mutation with an output schema, the description covers purpose, exclusions, recipient resolution, number scoping, and side effects. Nothing an agent needs to invoke it correctly is missing.

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, but the description adds a real cross-parameter constraint: the message must belong to the number named by `number_alias`, else not found. It also explains how the recipient is derived from the original message rather than supplied, which is meaning the schema cannot express.

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 — replying to an EARLIER message by quoting it — and immediately contrasts with `send_text` for the just-received case. The behavior is distinguishable from every listed sibling 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 Guidelines5/5

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

Gives an explicit when-to-use condition (the conversation moved on and the answer depends on an earlier message) and an explicit when-not-to-use with the named alternative (`send_text`). Nothing about tool selection is left to inference.

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.