Skip to main content
Glama

Delete Message

neuron_delete_message
Destructive

Permanently deletes a specific message from a conversation using the conversation and message IDs.

Instructions

Delete a specific message from a conversation. This action cannot be undone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe unique identifier of the conversation
msgIdYesThe unique identifier of the message to delete
Behavior3/5

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

Annotations already provide destructiveHint: true. The description adds 'cannot be undone' which reinforces the destructive nature but does not disclose additional behavioral traits such as authorization requirements, rate limits, or effects on conversation history.

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 extremely concise with two sentences, no wasted words. Every sentence earns its place by stating the core action and emphasizing irreversibility.

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 delete tool with no output schema, the description is complete. It covers the purpose and the critical behavioral note (cannot be undone). The schema fully specifies the required parameters.

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 coverage is 100% with both parameters described in the schema. The description does not add any new meaning beyond what the schema already provides, so baseline score of 3 is appropriate.

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 clearly states the verb 'delete' and the resource 'a specific message from a conversation'. It distinguishes itself from sibling tools like neuron_edit_message (which edits) and other delete tools (e.g., neuron_delete_bot).

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 description mentions the action cannot be undone, which is a warning but does not provide explicit guidance on when to use this tool versus alternatives (e.g., editing a message or deleting a whole conversation). No exclusions or alternative suggestions are given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/conquext/neuron-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server