Skip to main content
Glama

get_emoji_likes

Read-only

Retrieves the list of users who reacted to a specific QQ message with a given emoji, using the message ID and emoji ID.

Instructions

获取表情回应用户 使用消息事件或发送结果中的真实 message_id,负值合法;消息须在当前账号的消息存储中可查询。 Returns: { emoji_like_list }:回应该表情的用户列表(nick_name 恒为空串)。

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": "get_emoji_likes"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 establish readOnlyHint=true, destructiveHint=false, openWorldHint=true, and the description usefully adds that the target message must exist in the current account's store and that negative message_ids are accepted. It also flags a surprising output quirk (nick_name is always an empty string), which is real behavioral value. It still says nothing about what happens when the message is not found or about result size/limits.

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?

Dense and front-loaded: purpose first, then the operational constraints, then the return shape. Every clause carries information; the only slight cost is the mixed Chinese/English formatting that could slow parsing, but no sentence is wasted.

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?

No output schema exists, yet the description supplies the return key and a caveat about the returned nick_name field, plus the message-store precondition – enough for an agent to call and interpret it. The gap is only the undocumented emoji_id semantics.

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 must carry parameter meaning; it does explain that message_id must come from event/send payloads and documents the negative-value edge case (consistent with the schema's not-const-0 constraint). However, emoji_id is never described at all – no format, source, or how to obtain a valid emoji id – leaving one of two required parameters undocumented.

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?

States a specific verb and resource: retrieve the users who reacted to a message with a given emoji, and even previews the return key (emoji_like_list). It is clear on its own, but it never contrasts itself with the near-identical siblings (get_msg_emoji_likes, fetch_emoji_like), so an agent must guess which of the three to pick.

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?

Gives concrete preconditions for use: the message_id must be a real id from a message event or send result, negative values are legal, and the message must be queryable in the current account's message store. That tells the agent when the call will succeed, but offers no explicit when-to-use versus alternatives or when-not rules.

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