Skip to main content
Glama

给消息加表情回应 / 查看 / 撤掉

feishu_reaction

Manage reactions on Feishu messages: add emoji acknowledgements, list who responded, or remove bot-added reactions to keep chats uncluttered.

Instructions

表情回应是飞书里最轻的「我看到了 / 收到 / 干完了」信号,不占聊天版面。action=add 加一个(emoji_type 用飞书的表情名,如 SMILE、THUMBSUP、DONE、OK、HEART);action=list 看这条消息上有谁回应了什么(返回 reaction_id,撤掉时要用);action=remove 撤掉一个(只能撤机器人自己加的)。

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": {
      "action": "<action>",
      "message_id": "<message_id>"
    },
    "name": "feishu_reaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesadd 加、list 看、remove 撤。
emoji_typeNoaction=add 必填,飞书表情名,如 SMILE / THUMBSUP / DONE / OK / HEART。
message_idYes消息 id(om_ 开头)。
reaction_idNoaction=remove 必填,来自 action=list 返回的 reaction_id。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description adds real behavioral context on top: that remove is restricted to the bot's own reactions, and that list returns reaction_id which is the prerequisite input for remove. That is a meaningful dependency chain the agent could not infer from annotations. It does not cover failure modes (e.g. adding a duplicate reaction, invalid emoji names) or what add returns.

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?

A single compact paragraph with the purpose front-loaded and each action enumerated in order. The parenthetical examples earn their place by showing emoji naming convention, though the emoji name list is duplicated verbatim from the schema.

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

Completeness4/5

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

With 4 parameters at full schema coverage and no output schema, the definition covers all actions plus the two constraints an agent most needs (emoji naming, bot-only removal, reaction_id round-trip). The remaining gap is return shape for add and list beyond reaction_id, which is minor for this complexity.

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%, and the schema already documents action, emoji_type examples, message_id format, and the reaction_id provenance. The description largely restates those same points (emoji names, reaction_id from list), adding little beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 names a specific resource (message reactions) and spells out all three modes — add a reaction, list who reacted with what, remove one — so an agent knows exactly what the tool does. It does not explicitly contrast itself with siblings like feishu_reply or feishu_pin, but the resource is distinct enough that confusion is unlikely.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a genuine usage framing — reactions are the lightest 'seen / got it / done' signal that doesn't consume chat space — which implicitly tells the agent to prefer this over sending a message for acknowledgement. It also states the key constraint that removal only applies to reactions the bot itself added. No explicit when-not guidance or named alternatives, so it stops short of a 5.

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