Skip to main content
Glama

Coline

Edit message

edit_message
DestructiveIdempotent

Rewrites one of the person's own messages.

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": {
      "workspace": "<workspace>",
      "messageId": "<messageId>"
    },
    "name": "edit_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoThe new message, in markdown. Or give content.
typeNo
contentNo
messageIdYesMessage id from read_conversation.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
conversationIdNoFrom list_conversations.

Output Schema

NameRequiredDescriptionDefault
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=true, so the safety profile is covered. The description adds genuinely useful context by restricting edits to the person's own messages (an authorization constraint not in the annotations), and "Rewrites" is consistent with destructive whole-message replacement. It does not say whether prior content is recoverable, whether notification happens, or whether edits are time-limited.

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?

A single lean sentence with no filler and the ownership constraint front and center. Its brevity is close to under-specification rather than excess, so it is efficient but thin.

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?

For a destructive mutation with six parameters and an existing output schema, the definition omits key operational context: whether the whole message body is overwritten, whether that is reversible, and how the text/content alternatives differ. The output schema removes the need to explain return values, but the mutation semantics remain unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description mentions no parameters at all, while the schema sits at 67% coverage with six parameters, and the ambiguous text-vs-content alternation (two ways to supply the new body) is left entirely to the schema. Nothing in the description clarifies whether text replaces the whole message body or how type/conversationId interact with the edit.

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?

States a specific verb and resource ("Rewrites ... messages") and adds an ownership scope ("one of the person's own"), which separates it from send_message and delete_message without naming them. It stops short of distinguishing itself from other message mutations such as pin_message, but the intent is unambiguous.

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?

There is no explicit when-to-use guidance, no exclusion of alternatives, and no stated prerequisites beyond the implied ownership restriction. An agent must infer from the name alone that this is the tool for changing an existing message rather than creating or reacting to one.

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.

Resources