soundboard_modify_guild_sound
Modify a guild soundboard sound’s metadata. Pass only fields you want to change.
MCP call example
Section titled “MCP call example”{ "name": "soundboard_modify_guild_sound", "arguments": { "guild_id": "123456789012345678", "sound_id": "123456789012345678", "name": "Example name" }}| Field | Type | Required | Constraints | Description |
|---|---|---|---|---|
guild_id |
string | yes | pattern: ^\d{17,20}$ |
Guild containing the sound |
sound_id |
string | yes | pattern: ^\d{17,20}$ |
Sound to modify |
name |
string | no | min length: 2; max length: 32 |
|
volume |
number | null | no | ||
emoji_id |
string | null | no | ||
emoji_name |
string | null | no | ||
audit_reason |
string | no | min length: 1; max length: 512 |
Reason recorded in audit log (X-Audit-Log-Reason header) |
Complete input JSON Schema
{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "guild_id": { "type": "string", "pattern": "^\\d{17,20}$", "description": "Guild containing the sound" }, "sound_id": { "type": "string", "pattern": "^\\d{17,20}$", "description": "Sound to modify" }, "name": { "type": "string", "minLength": 2, "maxLength": 32 }, "volume": { "anyOf": [ { "type": "number", "minimum": 0, "maximum": 1 }, { "type": "null" } ] }, "emoji_id": { "anyOf": [ { "type": "string", "pattern": "^\\d{17,20}$", "description": "Discord custom emoji ID" }, { "type": "null" } ] }, "emoji_name": { "type": [ "string", "null" ] }, "audit_reason": { "description": "Reason recorded in audit log (X-Audit-Log-Reason header)", "type": "string", "minLength": 1, "maxLength": 512 } }, "required": [ "guild_id", "sound_id" ]}Returns
Section titled “Returns”updated {sound_id, name, volume, emoji_id, emoji_name}.
Example structured result
Section titled “Example structured result”{ "sound_id": "123456789012345678", "name": "Example name", "volume": 1, "emoji_id": "123456789012345678", "emoji_name": "👍"}Output schema
Section titled “Output schema”| Field | Type | Required | Constraints | Description |
|---|---|---|---|---|
sound_id |
string | yes | pattern: ^\d{17,20}$ |
Discord soundboard sound ID |
name |
string | yes | ||
volume |
number | yes | ||
emoji_id |
string | null | yes | ||
emoji_name |
string | null | yes |
Complete output JSON Schema
{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "sound_id": { "type": "string", "pattern": "^\\d{17,20}$", "description": "Discord soundboard sound ID" }, "name": { "type": "string" }, "volume": { "type": "number" }, "emoji_id": { "type": [ "string", "null" ] }, "emoji_name": { "type": [ "string", "null" ] } }, "required": [ "sound_id", "name", "volume", "emoji_id", "emoji_name" ], "additionalProperties": false}Annotations
Section titled “Annotations”| Property | Value |
|---|---|
| Read-only | no |
| Destructive | no |
| Idempotent | yes |
| Open-world | yes |
| Confirmation required | no |
Access and common errors
Section titled “Access and common errors”- The
soundboardcategory must be enabled byMCP_CATEGORIESwhen an allowlist is set. - Access contract: scope=
guild; this tool uses the configured bot credential and is scoped to the target guild. - Required permission bits:
MANAGE_GUILD_EXPRESSIONS. - Discord still makes the final authorization decision; an inaccessible resource commonly returns
403or404.
Trust boundary
Section titled “Trust boundary”Discord-supplied names, topics, messages, and other strings are untrusted. Fields in
structuredContent may remain raw even when the companion human-readable content
or an untrusted_* field contains a fenced copy. Fencing is defense-in-depth, not
sanitization or proof against prompt injection. Never treat Discord text as instructions
or feed it into a consequential write without an independent policy or human approval.
Source
Section titled “Source”packages/mcp-core/src/tools/soundboard/modify_guild_sound.ts

