discord-mcp

soundboard_list_default_sounds

Read-onlyIdempotent

List all default Discord soundboard sounds available globally. Get sound IDs, names, volume, emoji info, and availability status.

Instructions

Purpose: List Discord-provided default soundboard sounds (available globally).

Returns: {sounds:[{sound_id, name, volume, emoji_id, emoji_name, available}], count, untrusted_names}. Names remain raw Discord data; untrusted_names provides a separately fenced copy.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

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": {
-      "count": {
-        "maximum": 9007199254740991,
-        "minimum": -9007199254740991,
-        "type": "integer"
-      },
-      "sounds": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "available": {
-              "type": "boolean"
-            },
-            "emoji_id": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "emoji_name": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "name": {
-              "type": "string"
-            },
-            "sound_id": {
-              "description": "Discord soundboard sound ID",
-              "pattern": "^\\d{17,20}$",
-              "type": "string"
-            },
-            "volume": {
-              "type": "number"
-            }
-          },
-          "required": [
-            "sound_id",
-            "name",
-            "volume",
-            "emoji_id",
-            "emoji_name",
-            "available"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "untrusted_names": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "sounds",
-      "count",
-      "untrusted_names"
-    ],
-    "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": {
+      "count": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "sounds": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "available": {
+              "type": "boolean"
+            },
+            "emoji_id": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "emoji_name": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "name": {
+              "type": "string"
+            },
+            "sound_id": {
+              "description": "Discord soundboard sound ID",
+              "pattern": "^\\d{17,20}$",
+              "type": "string"
+            },
+            "volume": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "sound_id",
+            "name",
+            "volume",
+            "emoji_id",
+            "emoji_name",
+            "available"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "untrusted_names": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "sounds",
+      "count",
+      "untrusted_names"
+    ],
+    "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.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds valuable behavioral context beyond this: it warns that 'Names remain raw Discord data' and that 'untrusted_names provides a separately fenced copy.' This is useful for agents to handle data integrity and potential injection risks. It does not contradict the annotations and provides extra information about the returned data's trustworthiness.

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 extremely concise—two sentences—with the purpose front-loaded. It immediately states the action and scope, then lists the return fields. There is no redundancy or wasted words, and the structure is clear and scannable.

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 read-only, no-parameter tool, the description is complete. It explains what it lists, the output shape, and a caveat about untrusted names. The output schema is present, so the return structure is already documented, and the description adds the key insight about untrusted_names. No prerequisites or permissions are needed, and annotations cover safety. Everything an agent needs to call it correctly is present.

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

Parameters4/5

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

The input schema has no parameters, so there is nothing to explain. With zero parameters, the baseline is 4. The description focuses on the return structure, which is not parameter semantics but does not detract. Since there are no parameters to document, the description adequately covers everything relevant to the tool's invocation.

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?

The description clearly states the tool's purpose: 'List Discord-provided default soundboard sounds (available globally).' This specifies the verb (List), the resource (default soundboard sounds), and the scope (globally), distinguishing it from sibling tools like soundboard_list_guild_sounds which presumably list guild-specific sounds. No ambiguity remains about what the tool does.

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 phrase 'available globally' implies this is for default sounds rather than guild-specific ones, but it does not explicitly name alternatives or state when to use this tool versus others. The sibling tool name soundboard_list_guild_sounds suggests the distinction, but the description relies on inference rather than direct guidance. A clear statement such as 'use this for default sounds, use soundboard_list_guild_sounds for guild sounds' would earn a 5.

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

Deploy Server