Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

delete_recent_avatar

Destructive

Deletes a recent Discord avatar by its avatar ID so you can remove unwanted recent avatar entries from your account.

Instructions

Delete Recent Avatar. [DELETE /users/@me/avatars/{avatar_id}]

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": {
      "avatar_id": "<avatar_id>"
    },
    "name": "delete_recent_avatar"
  }
}

Input Schema

NameRequiredDescriptionDefault
avatar_idYesRecent avatar ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/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 safety profile is fully covered by structured data. The description adds only the endpoint mapping, and says nothing about irreversibility, whether the avatar is removed from the user's profile, auth scope required, or the response shape.

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 fragments, action front-loaded, no filler. Brevity here borders on under-specification rather than padding, so it earns credit for economy but not full marks for informativeness.

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 parameter, no output schema, annotations covering destructiveness), so the minimal description is close to sufficient. It is still missing the one thing an agent would most need: how to obtain a valid avatar_id, presumably via list_recent_avatars.

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?

There is a single required parameter with 100% schema description coverage ("Recent avatar ID"), so the schema carries the meaning. The description adds nothing about where such an ID comes from or its format, which is the baseline-3 outcome when coverage is high.

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 plus resource ("Delete Recent Avatar") and pins it to an HTTP route (DELETE /users/@me/avatars/{avatar_id}), so an agent knows exactly which resource is affected. It does not explicitly differentiate from siblings such as list_recent_avatars, leaving the read/delete distinction implicit in the verb.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to call this versus alternatives — notably list_recent_avatars, which is the obvious companion for discovering a valid avatar_id. No prerequisites, no post-deletion expectations, no exclusions.

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