discord-mcp

soundboard_get_guild_sound

Read-onlyIdempotent

Fetch a single Discord guild soundboard sound by its ID and guild ID. Returns details such as name, volume, and emoji metadata.

Instructions

Purpose: Fetch a single guild soundboard sound.

Returns: {sound_id, name, volume, emoji_id, emoji_name, guild_id, available, untrusted_text}. name remains raw Discord data; untrusted_text provides a separately fenced copy.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`guild_id`	Yes	Guild containing the sound
`sound_id`	Yes	Soundboard sound ID

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.28.0Sep 15, 2026

changedOutput schema / anyOf

Previous value: -[
-  {
-    "$schema": "https://json-schema.org/draft/2020-12/schema",
-    "additionalProperties": {},
-    "properties": {
-      "available": {
-        "type": "boolean"
-      },
-      "emoji_id": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "emoji_name": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "guild_id": {
-        "description": "Discord guild (server) ID",
-        "pattern": "^\\d{17,20}$",
-        "type": "string"
-      },
-      "name": {
-        "type": "string"
-      },
-      "sound_id": {
-        "description": "Discord soundboard sound ID",
-        "pattern": "^\\d{17,20}$",
-        "type": "string"
-      },
-      "untrusted_text": {
-        "type": "string"
-      },
-      "volume": {
-        "type": "number"
-      }
-    },
-    "required": [
-      "sound_id",
-      "name",
-      "volume",
-      "emoji_id",
-      "emoji_name",
-      "guild_id",
-      "available",
-      "untrusted_text"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "category": {
-        "enum": [
-          "client",
-          "server"
-        ],
-        "type": "string"
-      },
-      "code": {
-        "type": "string"
-      },
-      "recovery_hint": {
-        "type": "string"
-      },
-      "retriable": {
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "code",
-      "retriable",
-      "category",
-      "recovery_hint"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "$schema": "https://json-schema.org/draft/2020-12/schema",
+    "additionalProperties": {},
+    "properties": {
+      "available": {
+        "type": "boolean"
+      },
+      "emoji_id": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "emoji_name": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "guild_id": {
+        "description": "Discord guild (server) ID",
+        "pattern": "^\\d{17,20}$",
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "sound_id": {
+        "description": "Discord soundboard sound ID",
+        "pattern": "^\\d{17,20}$",
+        "type": "string"
+      },
+      "untrusted_text": {
+        "type": "string"
+      },
+      "volume": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "sound_id",
+      "name",
+      "volume",
+      "emoji_id",
+      "emoji_name",
+      "guild_id",
+      "available",
+      "untrusted_text"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "category": {
+        "enum": [
+          "client",
+          "server"
+        ],
+        "type": "string"
+      },
+      "code": {
+        "type": "string"
+      },
+      "recovery_hint": {
+        "type": "string"
+      },
+      "retriable": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "code",
+      "retriable",
+      "category",
+      "recovery_hint"
+    ],
+    "type": "object"
+  }
+]

First observedv0.22.0Aug 14, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds useful output-handling context by warning that `name` is raw Discord data while `untrusted_text` is a separately fenced copy, which is non-obvious and valuable for safe consumption.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded: a labeled Purpose section followed by a short Returns section. There is no filler, and the untrusted-text note earns its place as important caveat.

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

Completeness5/5

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

For a simple read-only get-by-ID operation, the description and annotations together cover purpose, required parameters, return shape, and the raw-vs-fenced trust distinction. No additional error, auth, or rate-limit detail is necessary for this level of complexity.

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%, and both `guild_id` and `sound_id` have clear descriptions as snowflake identifiers. The description adds no parameter semantics beyond what the schema already provides, so the baseline score applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb 'Fetch' and a specific resource 'a single guild soundboard sound', which clearly distinguishes it from sibling list/create/modify/delete sound tools. The word 'single' disambiguates it from soundboard_list_guild_sounds.

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

Usage Guidelines4/5

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

The description gives clear context: use this when retrieving one specific sound rather than enumerating sounds. It does not explicitly name sibling alternatives like soundboard_list_guild_sounds or state when not to use it, so it falls just short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server