Skip to main content
Glama
Sign In
feishu-user-plugin

feishu-user-plugin

by EthanQC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

delete_reaction

Deletes an emoji reaction from a message. Provide the message ID and reaction ID to remove the reaction.

Instructions

[Official API] Remove an emoji reaction from a message.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "message_id": "<message_id>",
      "reaction_id": "<reaction_id>"
    },
    "name": "delete_reaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYesMessage ID
reaction_idYesReaction ID (from add_reaction response)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.10

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action itself and omits important traits such as whether users can only remove their own reactions, idempotency, or failure behavior when the reaction does not exist.

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, concise sentence that is front-loaded with the action and object. The '[Official API]' prefix is minor noise but does not detract significantly.

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 simple delete operation, the description is minimally adequate but lacks critical context such as ownership requirements (whether the user must have added the reaction), behavior when the reaction is not found, and there is no output schema or annotations to fill these gaps.

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 provides descriptions for both parameters, achieving 100% coverage. The description adds no additional parameter semantics beyond what the schema already provides; the note 'from add_reaction response' is included in the schema, not the description.

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 uses a specific verb 'Remove' and clearly identifies the resource: 'an emoji reaction from a message'. This distinguishes it from sibling tools like 'add_reaction' and 'delete_message', making the tool's purpose 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?

No explicit guidance is provided on when to use this tool versus alternatives, nor are prerequisites or permission requirements mentioned. The context is implied by the tool's name and sibling set, but not stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools