Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_guild_soundboard_sounds

Read-only

Retrieves all soundboard sounds available in a Discord server (guild) so you can see which sounds members can play. Use the guild ID to fetch the current sound list.

Instructions

List Guild Soundboard Sounds. [GET /guilds/{guild_id}/soundboard-sounds]

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>"
    },
    "name": "list_guild_soundboard_sounds"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID

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=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The endpoint path confirms this is a direct Discord API passthrough, which is mildly useful context, but the description says nothing about pagination, result limits, or whether sounds are returned in a stable order.

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 short, front-loaded sentences with no filler or redundancy. It is terse rather than padded, though the endpoint path in brackets is of marginal value to an agent that already has annotations.

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

Completeness3/5

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

For a simple single-parameter read tool with full annotation coverage and full schema coverage, the essentials are present. The notable gaps are the absence of any return-shape or pagination note and the lack of differentiation from the closely named default-soundboard sibling.

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?

There is a single parameter with 100% schema description coverage ("Server (guild) ID"), so the schema already carries the semantics. The description adds no format hints or examples for guild_id, which is acceptable at this coverage level but is the baseline rather than an improvement.

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

Purpose3/5

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

The description restates the tool name almost verbatim ("List Guild Soundboard Sounds") and adds only the underlying endpoint path. It conveys the verb and resource, but an agent learns nothing about scope beyond what the name already implies, and nothing distinguishes it from the sibling list_default_soundboard_sounds.

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 guidance on when to use this tool versus list_default_soundboard_sounds, get_guild_soundboard_sound, or get_soundboard_sound_guild. The only implied context is the guild_id parameter, which the schema already supplies.

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