Skip to main content
Glama

fetch_emoji_like

Read-only

Retrieve a paginated list of users who reacted with a specific emoji to a QQ message by message ID, using cookies to fetch subsequent result pages.

Instructions

获取表情回应用户(NapCat 分页) 使用消息事件或发送结果中的真实 message_id,负值合法;消息须在当前账号的消息存储中可查询。 后续页原样传回上页 cookie。 Returns: 分页的表情回应用户列表(NapCat 形状),含分页游标 cookie 与首/末页标记。

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

Input Schema

NameRequiredDescriptionDefault
countNo
cookieNo
emojiIdYes
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=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context beyond that — negative message_id legality, the message-store preconditions, and cursor echo semantics. However, it says nothing about error behavior when the message is not in the store, or ordering of the returned users.

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?

Structure is good: capability first, then usage preconditions, then a clearly labelled 'Returns:' clause. The pagination advice sits after the message_id preconditions in a logical order, and no sentence is 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?

With no output schema, the description correctly spends a sentence on the return shape (paginated NapCat-shaped user list with cursor and first/last-page flags), which is the right call. But for a 4-parameter tool with a required emojiId whose semantics are undocumented, the definition is not quite complete enough for an agent to call it correctly on the first try.

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 the whole parameter burden — and it only documents two of four. message_id (real IDs, negatives allowed, must be queryable) and cookie (pass back unchanged) are well explained, but the required emojiId format (numeric id vs. unicode) and the meaning of count (including what count=0 does) are never addressed.

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+resource: fetching the users who reacted with an emoji, explicitly scoped to NapCat pagination. It is distinguishable from a generic likes-lookup, though it never names the closely related siblings (get_emoji_likes, get_msg_emoji_likes) to say how it differs from them.

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 real preconditions: the message_id must come from a message event or send result, negative values are valid, and the message must be queryable in the current account's message store. It also explains the continuation pattern (echo the previous page's cookie verbatim). The gap is that it offers no explicit alternative or exclusion relative to sibling reaction-listing 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