Skip to main content
Glama

remove_reaction

Delete an emoji reaction from a Slack message by specifying the channel, message timestamp, and emoji name.

Instructions

Remove an emoji reaction from a message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelYesChannel ID
timestampYesMessage timestamp
nameYesEmoji name (without colons)

Implementation Reference

  • The core handler function for the 'remove_reaction' tool. It validates input using removeReactionSchema, calls the Slack API to remove the reaction, and returns a success response.
    export async function removeReaction(client: SlackClientWrapper, args: unknown) {
      const params = removeReactionSchema.parse(args);
    
      return await client.safeCall(async () => {
        await client.getClient().reactions.remove({
          channel: params.channel,
          timestamp: params.timestamp,
          name: params.name,
        });
    
        return {
          ok: true,
          channel: params.channel,
          timestamp: params.timestamp,
          reaction: params.name,
        };
      });
    }
  • Zod schema for validating the input parameters of the remove_reaction tool: channel ID, message timestamp, and emoji name.
    export const removeReactionSchema = z.object({
      channel: channelIdSchema,
      timestamp: timestampSchema,
      name: emojiSchema,
    });
  • src/index.ts:374-395 (registration)
    Tool registration metadata including name, description, and input schema definition used in list_tools response.
    {
      name: 'remove_reaction',
      description: 'Remove an emoji reaction from a message',
      inputSchema: {
        type: 'object',
        properties: {
          channel: {
            type: 'string',
            description: 'Channel ID',
          },
          timestamp: {
            type: 'string',
            description: 'Message timestamp',
          },
          name: {
            type: 'string',
            description: 'Emoji name (without colons)',
          },
        },
        required: ['channel', 'timestamp', 'name'],
      },
    },
  • src/index.ts:438-438 (registration)
    Handler function registration in the toolHandlers map, binding 'remove_reaction' to the implementation in reactionTools.
    remove_reaction: (args) => reactionTools.removeReaction(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. While 'Remove' implies a destructive mutation, the description doesn't specify whether this requires specific permissions, is reversible, has side effects, or what happens on success/failure. For a mutation tool with zero annotation coverage, this leaves critical behavioral traits undocumented.

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 that directly states the tool's purpose with zero redundant words. It's appropriately sized for a simple operation and front-loads the core action, 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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks information about permissions, side effects, error conditions, or return values. While the schema covers parameters well, the overall context for safe and effective use is insufficient for a tool that modifies data.

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 100%, with all three parameters clearly documented in the schema (channel ID, message timestamp, emoji name). The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints. The baseline score of 3 reflects adequate coverage by the schema alone.

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 specific action ('Remove') and target resource ('an emoji reaction from a message'), distinguishing it from sibling tools like 'add_reaction' (which adds reactions) and 'delete_message' (which deletes entire messages). The verb+resource combination is precise and 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 description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing appropriate permissions), when not to use it, or how it differs from similar tools like 'delete_message' for message removal. The agent must infer usage solely from the tool name and description.

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