Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

messages_edit

Edit the text of a message you already sent, in place. Supported on Telegram, WhatsApp, LiveChat, Max.ru, LINE, WeChat and similar channels; NOT supported on Gmail, Instagram, or LinkedIn (their platforms forbid editing) — those return an explicit error. Note: channels impose their own limits (own messages only, edit time windows such as ~48h on Telegram / ~15min on WhatsApp).

Get the message_id from messages.read_history (each row's id).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
new_textYesReplacement text for the message.
thread_idYesThread ID containing the message (numeric DB id or channel_ref like 'telegram:-100123').
message_idYesID of the message to edit (from messages.read_history).
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
+  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+  "type": "integer"
+}
  2. Added
  3. Removed
  4. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so safety is partly covered. The description goes beyond this by disclosing own-messages-only restriction, channel-specific edit windows (~48h Telegram / ~15min WhatsApp), and explicit errors on unsupported platforms. It stops short of describing what happens to the prior text/formatting on success, so a 4 rather than 5.

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?

Core action is front-loaded in the first clause, with support matrix and constraints following. The channel enumeration is somewhat lengthy but each list element carries routing value; there is no filler sentence.

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 covers the important non-obvious risks: unsupported-platform errors, ownership restriction, and time windows. It does not describe the success return payload, but for an in-place edit that is a minor omission given how thoroughly the failure modes are covered.

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 all four parameters are already documented, and the description's pointer to messages.read_history for message_id duplicates the schema note ('from messages.read_history'). Baseline 3 applies since the schema does the heavy lifting and the prose adds no new syntax or format detail.

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 ('Edit the text of a message you already sent, in place'), which cleanly distinguishes it from messages_send, messages_forward, and messages_delete. An agent can tell exactly what operation this performs without opening the 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?

Explicitly names supported channels (Telegram, WhatsApp, LiveChat, Max.ru, LINE, WeChat) and excluded ones (Gmail, Instagram, LinkedIn), with the reason ('their platforms forbid editing') and the behavior on failure ('return an explicit error'). It also gives the prerequisite path for obtaining message_id via messages.read_history.

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

All dialogbrain toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources