Skip to main content
Glama

add_reaction

Add emoji reactions to Slack messages using channel ID, timestamp, and emoji name to express responses or acknowledge content.

Instructions

Add an emoji reaction to a message

Input Schema

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

Implementation Reference

  • The core handler function that parses arguments using the schema, calls Slack's reactions.add API via the client wrapper, and returns a success response.
    export async function addReaction(client: SlackClientWrapper, args: unknown) {
      const params = addReactionSchema.parse(args);
    
      return await client.safeCall(async () => {
        await client.getClient().reactions.add({
          channel: params.channel,
          timestamp: params.timestamp,
          name: params.name,
        });
    
        return {
          ok: true,
          channel: params.channel,
          timestamp: params.timestamp,
          reaction: params.name,
        };
      });
    }
  • Zod schema defining the input parameters for the add_reaction tool: channel ID, message timestamp, and emoji name.
    export const addReactionSchema = z.object({
      channel: channelIdSchema,
      timestamp: timestampSchema,
      name: emojiSchema,
    });
  • src/index.ts:352-373 (registration)
    Tool specification registered for the list_tools endpoint, including name, description, and JSON schema matching the Zod schema.
    {
      name: 'add_reaction',
      description: 'Add an emoji reaction to 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:437-437 (registration)
    Handler mapping in the toolHandlers object that wires the 'add_reaction' tool name to the imported addReaction function.
    add_reaction: (args) => reactionTools.addReaction(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 'Add' implies a write/mutation operation, it doesn't specify permissions required, rate limits, whether reactions are reversible, 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 with zero wasted words. It is front-loaded with the core action and resource, making it immediately understandable. Every word earns its place by conveying essential purpose without redundancy.

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 (adding reactions) with no annotations and no output schema, the description is incomplete. It lacks information on behavioral aspects like permissions, side effects, error handling, or return values. For a tool that modifies data, more context is needed to ensure safe and correct usage by an AI agent.

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 clear parameter descriptions in the schema (e.g., 'Channel ID', 'Message timestamp', 'Emoji name (without colons)'). The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline 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.

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 ('Add an emoji reaction') and the target resource ('to a message'), using precise terminology. It effectively distinguishes this tool from sibling tools like 'remove_reaction' (which performs the opposite action) and 'send_message' (which creates content rather than reacting to it).

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 message access), exclusions (e.g., not for threads or files), or comparisons to similar tools like 'remove_reaction' or 'update_message' for editing reactions. Usage is implied but not explicitly defined.

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