Skip to main content
Glama

modify_custom_face

Updates the note or remark for a saved custom emoji by using its emoji_id, which you can obtain from fetch_custom_face_detail.

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

Input Schema

NameRequiredDescriptionDefault
descNo
emoji_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/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 covered. The description adds real value by narrowing scope to the remark only (not the emoji asset itself), but it does not say what an empty desc does (clearing the remark), whether the change is reversible, or what the response contains.

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, front-loaded with the action and followed by the key dependency. No filler, though the extreme brevity leaves the desc semantics unaddressed rather than being wasteful.

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 2-parameter mutation with no output schema, the definition covers identity and ID sourcing but omits the one behavior an agent could get wrong: what desc="" means. A single added clause on clearing semantics would make it complete.

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 param meaning. It explains emoji_id's source and, via 备注, implies desc is the new remark text, but it ignores the schema default of empty string for desc, leaving the clear/no-op ambiguity unresolved.

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: modify the remark (备注) of a favorited custom emoji. It also identifies emoji_id's provenance (fetch_custom_face_detail), which distinguishes it from add/delete/fetch siblings, though the title-less Chinese description leaves the actor (the remark field vs. the emoji) slightly implicit.

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' gives a clear prerequisite and points to the sibling that supplies the ID, which is genuinely useful routing. There is no statement of when to prefer this over add_custom_face or delete_custom_face, nor any exclusion or precondition beyond the ID source.

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