Skip to main content
Glama
zencoderai

Slack

by zencoderai

Add Slack Reaction

slack_add_reaction

Add a reaction emoji to a Slack message. Specify the channel ID, message timestamp, and emoji name to react instantly.

Instructions

Add a reaction emoji to a message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYesThe ID of the channel containing the message
timestampYesThe timestamp of the message to react to
reactionYesThe name of the emoji reaction (without ::)

Implementation Reference

  • Type definition AddReactionArgs for the slack_add_reaction tool input parameters (channel_id, timestamp, reaction).
    interface AddReactionArgs {
      channel_id: string;
      timestamp: string;
      reaction: string;
    }
  • index.ts:285-302 (registration)
    Registration of the slack_add_reaction tool with server.registerTool, including title, description, and Zod inputSchema.
    server.registerTool(
      "slack_add_reaction",
      {
        title: "Add Slack Reaction",
        description: "Add a reaction emoji to a message",
        inputSchema: {
          channel_id: z.string().describe("The ID of the channel containing the message"),
          timestamp: z.string().describe("The timestamp of the message to react to"),
          reaction: z.string().describe("The name of the emoji reaction (without ::)"),
        },
      },
      async ({ channel_id, timestamp, reaction }) => {
        const response = await slackClient.addReaction(channel_id, timestamp, reaction);
        return {
          content: [{ type: "text", text: JSON.stringify(response) }],
        };
      }
    );
  • Handler function that receives channel_id, timestamp, reaction and calls slackClient.addReaction(), returning the response.
    async ({ channel_id, timestamp, reaction }) => {
      const response = await slackClient.addReaction(channel_id, timestamp, reaction);
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    }
  • Helper method addReaction on SlackClient class that calls Slack API reactions.add with channel, timestamp, and reaction name.
    async addReaction(
      channel_id: string,
      timestamp: string,
      reaction: string,
    ): Promise<any> {
      const response = await fetch("https://slack.com/api/reactions.add", {
        method: "POST",
        headers: this.botHeaders,
        body: JSON.stringify({
          channel: channel_id,
          timestamp: timestamp,
          name: reaction,
        }),
      });
    
      return response.json();
    }
Behavior2/5

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

No annotations provided, so the description must cover behavioral traits. It only states the action without disclosing idempotency, error handling, or what happens if the reaction already exists.

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

Conciseness4/5

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

The description is a single clear sentence, front-loaded and to the point. Could be slightly more informative without harming conciseness.

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

Completeness3/5

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

For a simple tool with no output schema, the description provides basic understanding but lacks details on return values or error states.

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% and the description adds no additional meaning beyond the schema. Baseline is 3.

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?

Description clearly states the action (Add) and resource (reaction emoji to a message). It is distinct from sibling tools, which involve reading channels or posting messages.

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?

No guidance on when to use this tool versus alternatives. The description does not specify prerequisites or when not to use it.

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/zencoderai/slack-mcp-server'

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