Skip to main content
Glama

get_msg_emoji_likes

Read-only

Retrieve all emoji reactions on a QQ message by its real message_id, including each emoji's ID, reaction count, and users who reacted.

Instructions

获取一条消息的全部表情回应 使用消息事件或发送结果中的真实 message_id,负值合法;消息须在当前账号的消息存储中可查询。 Returns: 该消息上每个表情回应的编号、数量与用户列表。

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

Input Schema

NameRequiredDescriptionDefault
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered; the description adds real behavioral context beyond that: negative message_id values are legal, and the target message must exist in the current account's message store, which implies an empty/error outcome otherwise. It still doesn't say what happens when no reactions 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?

Two compact clauses — behavior/preconditions first, then a 'Returns:' summary — with no filler. The mixed-language phrasing is slightly harder to parse but nothing is redundant.

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?

For a one-parameter read-only tool with no output schema, the definition covers the critical unknowns: where to source the id, that negatives are valid, the storage precondition, and the shape of the returned data (code, count, user list). Sufficient for an agent to call correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single parameter, so the description must carry the meaning, and it does: it identifies the parameter as the message's real message_id sourced from events or send results and explicitly notes negative values are legal. The only missing piece is the non-zero constraint that appears in the schema as not const 0.

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 states a specific verb and resource: '获取一条消息的全部表情回应' (get all emoji reactions on one message), with the scope '全部' signaling it returns all reactions rather than one emoji's likers. It does not name the nearest sibling (get_emoji_likes) to draw the contrast explicitly, so it falls short of a 5.

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

Usage Guidelines3/5

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

It provides useful preconditions — use a real message_id from a message event or send result, negative values are valid, and the message must be queryable in the current account's store — but it never says when to prefer this over get_emoji_likes or fetch_emoji_like. Usage is implied through prerequisites rather than explicit routing guidance.

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