Skip to main content
Glama

remove-emoji-reaction

Remove emoji reactions from Zulip messages by specifying message ID and emoji name to clean up reactions or correct accidental additions.

Instructions

Remove an emoji reaction from a message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
message_idYesID of the message to remove reaction from
emoji_nameYesEmoji name to remove (e.g., 'thumbs_up', 'heart')
emoji_codeNoUnicode code point for the emoji
reaction_typeNoType of emoji reaction

Implementation Reference

  • MCP tool handler function that executes the remove-emoji-reaction logic by calling the Zulip client's removeReaction method and handling responses/errors.
    server.tool(
      "remove-emoji-reaction",
      "Remove an emoji reaction from a message.",
      RemoveReactionSchema.shape,
      async ({ message_id, emoji_name, emoji_code, reaction_type }) => {
        try {
          await zulipClient.removeReaction(message_id, {
            emoji_name,
            emoji_code,
            reaction_type
          });
          return createSuccessResponse(`Reaction ${emoji_name} removed from message ${message_id}!`);
        } catch (error) {
          return createErrorResponse(`Error removing reaction: ${error instanceof Error ? error.message : 'Unknown error'}`);
        }
      }
    );
  • Zod schema defining input parameters for the remove-emoji-reaction tool, used for validation.
    export const RemoveReactionSchema = z.object({
      message_id: z.number().describe("ID of the message to remove reaction from"),
      emoji_name: z.string().describe("Emoji name to remove (e.g., 'thumbs_up', 'heart')"),
      emoji_code: z.string().optional().describe("Unicode code point for the emoji"),
      reaction_type: z.enum(["unicode_emoji", "realm_emoji", "zulip_extra_emoji"]).optional().describe("Type of emoji reaction")
    });
  • src/server.ts:916-932 (registration)
    Registration of the remove-emoji-reaction tool in the MCP server using server.tool().
    server.tool(
      "remove-emoji-reaction",
      "Remove an emoji reaction from a message.",
      RemoveReactionSchema.shape,
      async ({ message_id, emoji_name, emoji_code, reaction_type }) => {
        try {
          await zulipClient.removeReaction(message_id, {
            emoji_name,
            emoji_code,
            reaction_type
          });
          return createSuccessResponse(`Reaction ${emoji_name} removed from message ${message_id}!`);
        } catch (error) {
          return createErrorResponse(`Error removing reaction: ${error instanceof Error ? error.message : 'Unknown error'}`);
        }
      }
    );
  • ZulipClient helper method that performs the actual API DELETE request to remove the emoji reaction from Zulip.
    async removeReaction(messageId: number, params: {
      emoji_name: string;
      emoji_code?: string;
      reaction_type?: string;
    }): Promise<void> {
      const queryParams = new URLSearchParams();
      queryParams.append('emoji_name', params.emoji_name);
      if (params.emoji_code) {queryParams.append('emoji_code', params.emoji_code);}
      if (params.reaction_type) {queryParams.append('reaction_type', params.reaction_type);}
      
      await this.client.delete(`/messages/${messageId}/reactions?${queryParams.toString()}`);
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'remove' implies a destructive operation, it doesn't specify permissions needed, whether the action is reversible, error conditions (e.g., if reaction doesn't exist), or what happens on success. This leaves significant behavioral gaps for a mutation tool.

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 communicates the core purpose without any wasted words. It's appropriately sized for a straightforward tool and front-loads the essential information.

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?

For a destructive mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after removal, error conditions, permissions required, or relationship to sibling tools. Given the complexity of a 4-parameter mutation operation, more context is needed.

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%, providing complete parameter documentation. The description adds no additional parameter information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in description.

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 clearly states the action ('remove') and resource ('emoji reaction from a message'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from its sibling 'add-emoji-reaction' beyond the verb difference, missing an opportunity for clearer sibling distinction.

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 an existing reaction to remove), when not to use it, or how it relates to sibling tools like 'add-emoji-reaction' or 'delete-message'.

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/avisekrath/zulip-mcp-server'

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