Skip to main content
Glama
serversmx

Evolution API MCP Server

by serversmx

evolution_chat_update_message

Edit a previously sent text message on WhatsApp by specifying the recipient, message key, and new text content.

Instructions

Edit a previously sent text message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesKey of the message to edit.
textYesNew text content.
numberYesRecipient phone number (digits, country code) or full WhatsApp JID.
instanceNoWhatsApp instance name. Optional if EVOLUTION_DEFAULT_INSTANCE is configured.
Behavior2/5

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

No annotations. Description does not disclose if editing is destructive, time-limited, or requires message ownership (though 'fromMe' key implies it). Lacks behavioral details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Single sentence is concise but under-specified. Better to add key context without being verbose; current version is too brief to be fully effective.

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

Completeness2/5

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

Given 4 parameters, nested object, no output schema, and no annotations, description is incomplete. Omits how to obtain key, purpose of number, etc.

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 covers all 4 parameters with descriptions. Baseline 3 as description adds no extra meaning; nested key object is described in schema.

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?

Description clearly states verb 'edit' and resource 'previously sent text message'. Distinguishes from delete and send tools, but could specify scope (e.g., only own messages).

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?

No guidance on when to use this tool vs alternatives like delete_message or send_text. Does not specify prerequisites or scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/serversmx/mcp-evolution-api'

If you have feedback or need assistance with the MCP directory API, please join our Discord server