Skip to main content
Glama

set_msg_emoji_like

Set or remove an emoji reaction on a QQ message using its real message_id, so AI agents can acknowledge or respond to messages. Use IDs from message events or send results; negative IDs are valid.

Instructions

设置消息表情回应 使用消息事件或发送结果中的真实 message_id,负值合法;消息须在当前账号的消息存储中可查询。

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>",
      "emoji_id": "<emoji_id>"
    },
    "name": "set_msg_emoji_like"
  }
}

Input Schema

NameRequiredDescriptionDefault
setNo
emoji_idYes
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds a genuine precondition (the message must be retrievable in the account's store) and the negative-id rule, but stays silent on what the `set` toggle does and what happens on failure or when the message is out of range.

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 purpose is front-loaded in the first clause, and the remaining clauses are compact semicolon-separated constraints. Every clause is informative, with no filler.

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 mutation tool with no output schema and three parameters, the definition covers the riskiest input (message_id) but leaves emoji_id and the `set` toggle undocumented in both schema and description. An agent could call it, but would be guessing on how to remove a reaction or what emoji_id format is accepted.

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 0%, so the description carries the burden. It usefully explains message_id semantics, including that negative values are legal (consistent with the schema's not-const-0 constraint), but says nothing about the format or constraints of emoji_id or the purpose of the boolean `set` parameter.

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 opens with a specific verb and resource: setting an emoji reaction on a message. That clearly separates it from the read-side siblings like get_msg_emoji_likes and fetch_emoji_like, though those alternatives are never named explicitly.

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 concrete sourcing rule for message_id (take the real id from message events or send results) and states the precondition that the message must exist in the current account's message store. That is real invocation guidance, though it does not contrast this tool with sibling reaction tools.

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