Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

delete_guild_soundboard_sound

Destructive

Deletes a soundboard sound from a Discord server by guild and sound ID, with an optional audit log reason.

Instructions

Delete a soundboard sound. [DELETE /guilds/{guild_id}/soundboard-sounds/{sound_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>",
      "sound_id": "<sound_id>"
    },
    "name": "delete_guild_soundboard_sound"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
guild_idYesServer (guild) ID
sound_idYesSoundboard sound ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 safety profile is covered structurally. The description adds only the API route; it does not say the deletion is permanent/irreversible, what permissions are required, or that the optional reason surfaces in the audit log.

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, front-loaded sentences with the action first and the endpoint mapping second; nothing is wasted, though the endpoint bracket is redundant for an agent that already has the tool signature.

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 simple destructive delete, annotations plus a fully documented 3-parameter schema cover most of what an agent needs. The description still leaves out irreversibility and permission requirements, which matter for a destructive 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 description coverage is 100%, with guild_id, sound_id and reason all documented in the schema, so the baseline applies. The description adds no parameter meaning beyond what the schema already provides.

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: delete a soundboard sound, with the exact REST endpoint in brackets. It is clearly distinguishable from create/get/modify soundboard siblings, though it doesn't say how it differs from other delete_* guild tools.

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?

No when-to-use or when-not-to-use guidance, no prerequisites, no mention of alternatives. An agent must infer that this is the tool for removing a guild soundboard sound rather than, say, sending or listing one.

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