Skip to main content
Glama

Coline

Delete message

delete_message
DestructiveIdempotent

Deletes one of the person's own messages for everyone.

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": "delete_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
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

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds one genuinely new behavioral fact — deletion applies 'for everyone', not just the caller — but omits whether permission is required, whether replies/threads are affected, or whether the action is reversible.

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 front-loaded sentence with the scope qualifier attached directly to the verb; nothing is wasted, though the terseness leaves behavioral gaps that a second clause could have closed.

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, irreversible-sounding operation with four parameters, the definition leaves out permissions, side effects on threads or recipients, and confirmation requirements. The presence of an output schema and rich annotations offsets some of this, but not enough for a mutation tool.

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 75%, with messageId, workspace and conversationId all documented in the schema, so the structured data does most of the work. The description adds nothing about parameters; only the 'own messages' clause hints at an ownership precondition for messageId.

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 ('Deletes ... messages') plus a scope qualifier ('for everyone') and an ownership constraint ('one of the person's own messages'). It does not explicitly distinguish itself from siblings such as edit_message or delete_channel, but the message-level target 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?

The only usage signal is the implicit restriction to messages the person owns; there is no statement of when to prefer this over edit_message or other message tools, and no prerequisites or exclusions are given.

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