Skip to main content
Glama
cappyeo

discord-mcp

by cappyeo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

soundboard_list_guild_sounds

Read-onlyIdempotent

List all custom soundboard sounds for a Discord guild by providing its ID. Returns sound names, count, and fenced untrusted names for safe handling.

Instructions

Purpose: List a guild's custom soundboard sounds.

Returns: {sounds:[...], count, untrusted_names}. Names remain raw Discord data; untrusted_names provides a separately fenced copy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guild_idYesGuild to list sounds from

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.28.0
    • 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"
+  }
+]
  2. First observedv0.22.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds value beyond those structured fields by documenting the return shape and warning that names remain raw Discord data with a separately fenced untrusted_names copy, which is useful safety context.

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?

Two clearly labeled sections, Purpose and Returns, front-load the essential information and avoid filler. Every sentence contributes either to identifying the tool's function or understanding its output shape.

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 one-parameter read-only list tool with a fully documented input schema and an output schema, the description covers purpose, response shape, and the untrusted-names nuance. No critical information needed to invoke it correctly is missing.

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 the single guild_id parameter is already documented as 'Guild to list sounds from.' The description adds no additional parameter-level detail, so the schema carries the semantic load; the baseline 3 is appropriate.

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 opens with a specific verb and resource: 'List a guild's custom soundboard sounds.' The word 'custom' distinguishes it from the sibling soundboard_list_default_sounds, and the plural 'sounds' makes clear it is a list operation rather than a single-sound getter.

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

Usage Guidelines3/5

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

The purpose statement implies this tool is for retrieving a guild's custom sound effects, and 'custom' separates it from default-sound listing. However, it never explicitly names alternatives or states when not to use it, so the agent must infer routing from the tool name and phrasing.

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