Skip to main content
Glama

send_custom_face

Sends a saved custom QQ emoji by emoji ID or 32-character MD5 to a group or private chat, preserving its display style.

Instructions

发送账号收藏表情(emoji_id 或 MD5),保留表情显示样式 群聊和私聊目标只能提供一个;emoji_id 来自 fetch_custom_face_detail。 Returns: { message_id: number }

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

Input Schema

NameRequiredDescriptionDefault
user_idNo目标 QQ 号;与 group_id 二选一
emoji_idYes当前账号收藏表情的完整 ID 或 32 位 MD5
group_idNo目标群号;与 user_id 二选一
reply_toNo可选回复消息 ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare a non-read-only, open-world, non-destructive write, so the description's extra contribution is the target-exclusivity rule, the note that the emoji display style is preserved, and the explicit return shape { message_id: number }. Those are genuine behavioral facts beyond the structured fields; permissions, failure modes, and rate limits are still undisclosed.

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?

Short and front-loaded, with the core action and identifier formats in the first clause and the target constraint immediately after. The Chinese clauses run together without separators, making the boundary between the exclusivity rule and the ID-source note slightly harder to parse, but nothing 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?

Four parameters are fully schema-documented and the return value is stated inline even though no output schema exists, so an agent has what it needs to construct a call. Only the boundary conditions (what happens on an invalid face or a target the bot cannot reach) remain unstated.

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%, so every parameter is already documented, giving a baseline of 3. The description only reinforces that emoji_id may be a full ID or 32-character MD5 and points to where it comes from, adding marginal meaning beyond reply_to and the user/group pair.

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: sending the account's favorited custom face, with emoji_id or MD5 as the identifier. It names a sibling (fetch_custom_face_detail) as the ID source, which helps distinguish it from the generic send_image/send_msg family, though it never explicitly contrasts with those senders.

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 the key operating constraint up front: for group chat and private chat targets, only one may be supplied. It also tells the agent to obtain emoji_id from fetch_custom_face_detail, which is real routing guidance. It stops short of stating when to prefer this over send_image or send_msg for other image types.

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