Skip to main content
Glama

graph_update_chat_message

Edit the body of a chat message you sent by chat and message ID, using either HTML or plain text.

Instructions

Edit the body of a chat message.

You can only edit messages you sent.

Args: chat_id: The chat ID. message_id: The message ID to edit. message: New message body. When is_html is true, send explicit HTML; markdown is not converted. is_html: Whether the body is HTML content (default: True). Use false for plain text.

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": {
      "chat_id": "<chat_id>",
      "message_id": "<message_id>",
      "message": "<message>"
    },
    "name": "graph_update_chat_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idYes
is_htmlNo
messageYes
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose two non-obvious behaviors: the edit is restricted to the caller's own messages, and HTML is sent verbatim with no markdown conversion. It says nothing about failure modes when the message is not yours, whether edits are reversible or leave an edited marker, or what the response contains.

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?

The purpose and the ownership restriction are front-loaded in two short sentences, then parameter detail follows in a scannable args block. The parameter names restating themselves is minor waste, but the structure suits a four-parameter tool with no schema documentation.

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?

For a simple four-parameter mutation with no annotations and no output schema, the definition covers the action, the ownership precondition, and every parameter's meaning. The main remaining gap is the absence of any indication of failure behavior or return value, which matters since no output schema exists to fill it.

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 0%, so the description must compensate, and it documents all four parameters. The is_html note goes beyond the schema by explaining the default (true) and the practical consequence that markdown is not converted, which is genuinely useful semantics.

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 first sentence names a specific verb and resource ("Edit the body of a chat message"), which is unambiguous about what the call does. It implicitly separates this from channel-message and send/delete siblings by scoping to an existing chat message body, though it never names an alternative to sharpen that line.

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?

The ownership rule ("You can only edit messages you sent") is a hard precondition the agent needs, but it is a constraint rather than routing guidance. There is no explicit statement about when to prefer this over graph_send_chat_message, graph_delete_chat_message, or graph_update_channel_message; the intended use case is only implied.

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