Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_guild_soundboard_sound

Edits an existing Discord server soundboard sound's name, volume, or emoji and records an optional audit-log reason.

Instructions

Edit a soundboard sound. [PATCH /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": "modify_guild_soundboard_sound"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 the PATCH endpoint, which usefully signals partial-update semantics and the two path identifiers, but it says nothing about required permissions, what happens to omitted fields, or failure behavior.

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 sentences with the purpose front-loaded and no filler. The bracketed endpoint is dense but earns its place by encoding the HTTP method and path parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter mutation tool with no output schema and only mid-level schema coverage, the description leaves too much unsaid: which fields are optional, whether this replaces or merges, and what a successful response contains. Annotations cover safety but not these operational details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, below the threshold where the schema can carry the full burden, and the schema's own labels are thin ("Name", "Volume 0-1"). The description adds no meaning about which fields are editable, that only name/volume/emoji_name are patchable, or what the required IDs identify beyond the path template.

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 names a specific verb+resource pair ("Edit a soundboard sound") that is immediately distinguishable from the create/delete/get/list siblings by the verb alone. It stops short of explicitly stating how it differs from them, but the purpose is unambiguous.

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 mention of prerequisites, and no routing to alternatives (e.g. create vs delete vs get). The agent must infer from the verb that this is the mutation path for an existing sound.

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