Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

create_guild_soundboard_sound

Upload an MP3 or OGG soundboard sound (≤512KB, ≤5.2s) to a Discord server so members can use it as a custom sound.

Instructions

Upload a soundboard sound (mp3/ogg ≤512KB). [POST /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": "<name>",
      "sound": "<sound>"
    },
    "name": "create_guild_soundboard_sound"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName
soundYesSound file (mp3/ogg, ≤512KB, ≤5.2s): local file path, URL or data: URI
reasonNoReason (shown in the audit log)
volumeNo
guild_idYesServer (guild) ID
emoji_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the write nature and external reach are covered. The description adds only the mp3/ogg ≤512KB constraint, which is already stated in the schema for the sound parameter, and says nothing about required permissions, the audit-log effect of reason, or failure modes for oversized/unsupported files.

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?

One compact sentence plus the endpoint reference, constraint front-loaded, no filler. Every element earns its place and the endpoint notation is a useful anchor.

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 6-parameter mutating tool with no output schema, the definition is minimally adequate: it identifies the resource and file limits, but omits permission requirements, what the response contains, and how errors are surfaced. Annotations cover the safety profile, so the remaining gap is moderate rather than critical.

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 67%, so most parameters are already documented in the schema, and the description's format/size note duplicates the sound parameter description. It adds no meaning for name, volume, emoji_name, or reason beyond what the schema provides, so the baseline of 3 applies.

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?

The description gives a specific verb and resource ("Upload a soundboard sound") plus a format/size constraint, which cleanly separates it from the get/modify/delete/list soundboard siblings. It does not explicitly name those alternatives, so it stops short of a 5.

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 when-to-use guidance, no mention of prerequisites such as permissions or bot requirements, and no comparison to sibling tools like modify_guild_soundboard_sound or send_soundboard_sound. The agent must infer usage from the name alone.

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