Skip to main content
Glama

move_custom_face_to_front

Moves a saved QQ custom emoji to the front of the collection using its emoji_id.

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

Input Schema

NameRequiredDescriptionDefault
emoji_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is partly covered. Beyond that, the description adds nothing: it does not say whether the reordering persists, how other emojis' relative order is affected, or what happens if the emoji is not in the collection. For a mutation tool this is a notable gap.

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 short clauses with the action front-loaded and the parameter hint immediately after — no filler. The brevity is efficient, though it borders on under-specification for a state-changing operation.

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?

The tool is simple (one required string parameter, no nested objects, no output schema), so the description need not explain return values. Still, for a mutation with openWorldHint=true, it omits preconditions and side effects that an agent would want before invoking it.

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% and the only parameter is documented merely as a non-empty string, so the description must carry the burden. It does add real meaning by stating the provenance of emoji_id (fetch_custom_face_detail), but gives no format, example value, or failure mode for an invalid ID.

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 uses a specific verb+resource pair (move a favorited custom face to the front), which is distinct from siblings like add_custom_face, delete_custom_face, or move_group_file. It does not explicitly name a sibling it displaces, but the operation and target object are unambiguous.

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 workflow dependency, pointing the agent at the tool that supplies the required ID — which is genuine routing guidance. However, there is no statement of when to prefer this over modify_custom_face or what preconditions must hold (e.g., the face must already be favorited).

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