Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

delete_guild_sticker

Destructive

Permanently removes a sticker from a Discord server using its guild and sticker IDs, with an optional audit log reason. Use it to clean up unused or unwanted server stickers.

Instructions

Delete a sticker. [DELETE /guilds/{guild_id}/stickers/{sticker_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": {
      "guild_id": "<guild_id>",
      "sticker_id": "<sticker_id>"
    },
    "name": "delete_guild_sticker"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
guild_idYesServer (guild) ID
sticker_idYesSticker 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 known. The description adds nothing beyond them — no statement of irreversibility, required permissions, or audit-log behavior for the reason parameter, which is exactly the extra context a destructive tool benefits from.

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 very short clauses, with the action front-loaded and the endpoint mapping trailing. Nothing is wasted, though the bracketed route is largely redundant with the schema for an agent that isn't writing raw HTTP calls.

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?

Parameters and the destructive nature are fully covered by the schema and annotations, and no output schema exists to explain. What remains missing is permission requirements and irreversibility, which matter for a deletion tool with openWorld access.

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 all three parameters (guild_id, sticker_id, reason) are already documented, including the audit-log note on reason. The endpoint path only echoes the ID mapping; no additional meaning is contributed.

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?

Uses a specific verb+resource ('Delete a sticker') and the bracketed endpoint [DELETE /guilds/{guild_id}/stickers/{sticker_id}] confirms it is guild-scoped sticker deletion, distinguishing it from generic sticker reads. It stops short of naming how it differs from siblings like delete_guild_emoji or modify_guild_sticker.

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 when-to-use guidance, no prerequisites (e.g. Manage Emojis and Stickers permission), and no mention of alternatives such as modify_guild_sticker for non-destructive changes. The agent must infer everything about selection context.

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