nc-mcp-server

delete_message

DestructiveIdempotent

Remove a chat message from a Talk conversation when you are the author or moderator. Deleted messages are replaced with a 'Message deleted' placeholder.

Instructions

Delete a chat message from a Talk conversation.

Only the message author or a moderator can delete a message. The message is replaced with "Message deleted" in the conversation.

Args: token: The conversation token. message_id: The ID of the message to delete.

Returns: Confirmation message.

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": {
      "token": "<token>",
      "message_id": "<message_id>"
    },
    "name": "delete_message"
  }
}

Input Schema

Name	Required	Description	Default
`token`	Yes
`message_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Sep 21, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true), the description discloses two important behavioral details: the permission requirement and the fact that the message is replaced with 'Message deleted' rather than fully removed. This adds real context about side effects that annotations alone don't convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is tight and front-loaded: one-sentence purpose, two behavioral notes, then a labeled Args/Returns section. Every sentence earns its place, and no filler is present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter delete tool, this is complete: it covers purpose, permissions, behavior, parameters, and return. The presence of an output schema means the return value doesn't need detailed documentation, and nothing necessary for an agent to call it correctly is missing.

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 explain the parameters, and it does: token is the conversation token and message_id is the ID of the message to delete. This is sufficient for correct invocation, though it could add more context on how to obtain the token.

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?

The description opens with a specific verb and resource: 'Delete a chat message from a Talk conversation.' This clearly distinguishes it from sibling delete tools such as delete_comment, delete_task, and delete_file, so an agent can tell them apart without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides clear contextual guidance: only the message author or a moderator can delete, and the message is replaced with a placeholder. It doesn't explicitly name alternative tools or say when not to use it, but the scope 'chat message from a Talk conversation' plus the permission precondition gives enough direction for correct selection.

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

Deploy Server