Skip to main content
Glama

delete_custom_face

Destructive

Deletes a custom QQ emoji by emoji_id, using the ID from fetch_custom_face_detail. Use it to remove saved emoji from your QQ account.

Instructions

删除收藏表情 emoji_id 来自 fetch_custom_face_detail。

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

Input Schema

NameRequiredDescriptionDefault
emoji_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the risk profile is covered structurally. The description adds only the id provenance; it never states whether deletion is permanent, whether it only removes from the favorites list, or what happens on an invalid id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with the action front-loaded and the id provenance trailing as supporting detail. No filler, no restatement of the tool name.

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 one-parameter destructive tool with annotations covering the safety profile and no output schema, the description is close to sufficient. The main gap is the absence of any irreversibility or side-effect statement, which matters most for a delete operation.

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 coverage is 0% for the single parameter, so the description must carry the meaning — and it does partially by identifying fetch_custom_face_detail as the source of emoji_id. It still says nothing about the id's format or validity constraints beyond the schema's minLength=1.

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?

"删除收藏表情" is a specific verb+resource pair that separates this from the many other delete_* siblings (delete_msg, delete_friend, delete_group_file). It also names the sibling that supplies the identifier, though it does not explicitly contrast itself with any alternative delete path.

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?

The clause "emoji_id 来自 fetch_custom_face_detail" implies a prerequisite workflow (fetch detail first, then delete), which is useful implied usage. There is no statement of when not to use it, whether the emoji must exist, or what to do for an unknown id.

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