Skip to main content
Glama
Sign In
Discord MCP - Discord server management MCP for AI agents

Discord MCP - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create soundboard sound

create_soundboard_sound

Upload an MP3 or OGG audio URL as a Discord soundboard sound with a name, optional emoji, volume, and target server; files must be ≤512 KB and ≤5.2 seconds.

Instructions

Upload a soundboard sound from an audio URL: mp3 or ogg, up to 512 KB and 5.2 seconds. Servers start with eight sound slots; boosts add more.

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": {
      "name": "<name>",
      "sound_url": "<sound_url>"
    },
    "name": "create_soundboard_sound"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
emojiNoAn emoji to show with the sound.
guildNoGuild (server) name or ID. Omit to use the default guild.
volumeNoPlayback volume. Default 1.
sound_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false. The description adds real behavioral context beyond that: accepted formats (mp3, ogg), a 512 KB and 5.2-second limit, and the slot quota starting at eight with boosts adding more. It does not mention required permissions or error behavior, which would be the next level of detail.

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 sentences, zero filler, and the hard constraints are front-loaded before the quota note. Every clause carries enforceable information.

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 five-parameter creation tool with no output schema, it covers validation and quota well. It omits what the tool returns on success and what permission or precondition failure looks like, which an agent creating a resource would reasonably want.

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 coverage is 60%: emoji, guild, and volume already have schema descriptions, but name and sound_url do not. The description supplies validation meaning for sound_url (format, size, duration) that the bare uri-format schema lacks, but it says nothing about the name parameter or about usable defaults beyond what the schema states.

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: "Upload a soundboard sound from an audio URL." It is clearly distinct from sibling names like update_soundboard_sound, delete_soundboard_sound, and list_soundboard_sounds, though it doesn't explicitly contrast with them.

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 format and size limits imply that this is the creation path, and the audio constraints partially imply when it will fail. However, it never says when to use this instead of update_soundboard_sound or what to do when the sound already exists, so an agent must guess that routing.

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