Skip to main content
Glama

delete_message

Remove unwanted or incorrect messages from Slack channels using channel ID and message timestamp.

Instructions

Delete a message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelYesChannel ID
tsYesMessage timestamp

Implementation Reference

  • The main handler function that executes the delete_message tool logic: validates input with schema, calls Slack's chat.delete API, and returns confirmation.
    export async function deleteMessage(client: SlackClientWrapper, args: unknown) {
      const params = deleteMessageSchema.parse(args);
    
      return await client.safeCall(async () => {
        await client.getClient().chat.delete({
          channel: params.channel,
          ts: params.ts,
        });
    
        return {
          ok: true,
          channel: params.channel,
          ts: params.ts,
        };
      });
    }
  • Zod input validation schema defining required channel ID and message timestamp for the delete_message tool.
    export const deleteMessageSchema = z.object({
      channel: channelIdSchema,
      ts: timestampSchema,
    });
  • src/index.ts:217-234 (registration)
    Tool metadata registration in the list_tools handler: defines name, description, and JSON input schema for delete_message.
    {
      name: 'delete_message',
      description: 'Delete a message',
      inputSchema: {
        type: 'object',
        properties: {
          channel: {
            type: 'string',
            description: 'Channel ID',
          },
          ts: {
            type: 'string',
            description: 'Message timestamp',
          },
        },
        required: ['channel', 'ts'],
      },
    },
  • src/index.ts:428-428 (registration)
    Runtime handler binding in the call_tool dispatcher: maps delete_message calls to the messageTools.deleteMessage implementation.
    delete_message: (args) => messageTools.deleteMessage(slackClient, args),
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Delete a message' implies a destructive, irreversible mutation, but it doesn't specify permissions required, rate limits, whether deletions are permanent, or what happens to thread replies. For a destructive tool with zero annotation coverage, this is a significant gap in transparency.

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 a single, efficient sentence with zero wasted words. It is appropriately sized and front-loaded, directly stating the core function without unnecessary elaboration, making it easy for an agent to parse quickly.

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?

Given the tool's destructive nature, lack of annotations, and no output schema, the description is incomplete. It doesn't address critical context like error conditions (e.g., if the message doesn't exist), return values (e.g., success confirmation), or behavioral nuances, leaving the agent under-informed for safe and effective use.

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?

The input schema has 100% description coverage, with clear documentation for 'channel' (Channel ID) and 'ts' (Message timestamp). The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline score of 3 for high schema coverage without compensating value.

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?

The description 'Delete a message' clearly states the verb (delete) and resource (message), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'remove_reaction' or 'archive_channel' which also involve removal operations, so it doesn't reach the highest score.

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 description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing permission), exclusions (e.g., cannot delete system messages), or related tools like 'update_message' for editing instead of deleting. This leaves the agent with insufficient context for optimal selection.

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/Hais/slack-bot-mcp'

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