Permanently removes a single chat message by message ID; use when a message must be deleted and the destructive action cannot be undone.
Permanently delete a single message. Mirrors syntx.chats.deleteMessage. Issues DELETE /api/v1/chats/messages/{message_id} (no chat id in the path). This action is destructive and cannot be undone.
| Name | Required | Description | Default |
|---|---|---|---|
| message_id | Yes | Message id to delete (required). |
Changes observed during successful MCP inspections.
v0.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, it carries the behavioral burden well by stating the action is destructive and irreversible, and it identifies the underlying endpoint. It omits permissions or error behavior, but covers the key risks for a delete operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, front-loaded with the core action and immediately followed by the important destructive warning and endpoint detail. No wasted text.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter delete tool with no output schema, the description covers purpose, destructiveness, and the endpoint sufficiently for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the parameter is already documented. The description adds useful path context by clarifying there is no chat id in the URL, only message_id.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: permanently deleting a single message. It clearly distinguishes this from deleting a chat or file, and the scope is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Makes clear this is for permanent deletion of one message and warns that the action cannot be undone. It does not explicitly compare with siblings like delete-chat or toggle-message-favorite, but the destructive context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.