Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

send_soundboard_sound

Play a soundboard sound in the Discord voice channel you are connected to; join a voice channel first before triggering the sound.

Instructions

Play a soundboard sound in the voice channel you are connected to (join_voice_channel first). [POST /channels/{channel_id}/send-soundboard-sound]

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": {
      "channel_id": "<channel_id>",
      "sound_id": "<sound_id>"
    },
    "name": "send_soundboard_sound"
  }
}

Input Schema

NameRequiredDescriptionDefault
sound_idYesSoundboard sound ID
channel_idYesChannel ID (text, voice, thread, forum or DM channel)
source_guild_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the safety profile is covered; the description adds the voice-connection prerequisite and the HTTP endpoint. It does not explain effects of the call, whether the sound plays for all channel members, or what the response contains.

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?

One front-loaded sentence with the prerequisite in parentheses, followed by the endpoint mapping. Nothing is padded, though the bracketed REST path adds little for an agent choosing a tool.

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 three-parameter action with no output schema, the prerequisite and target channel are stated, which is the core need. It leaves open whether the sound must belong to the channel's guild and what happens on failure when not in voice.

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

Parameters2/5

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

Schema coverage is 67% and the description adds no meaning to any of the three parameters. Notably, source_guild_id exists to pull sounds from another server, and the description never hints at that cross-server capability.

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

Purpose4/5

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

States a specific verb and resource (play a soundboard sound) plus the target scope (the voice channel you are connected to), which separates it from sibling send_voice_channel_effect and send_custom_call_sound at a glance. It stops short of explicitly naming those siblings, so differentiation relies on the reader's inference.

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?

Includes an explicit precondition — join_voice_channel first — which is real when-to-use guidance. It offers no guidance on when to prefer this over adjacent tools (custom call sound, voice channel effect) or what to do if already playing another sound.

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