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

Update soundboard sound

update_soundboard_sound

Rename a Discord soundboard sound or adjust its volume to fit server audio needs. Specify the sound, optional new name, and volume level.

Instructions

Rename a soundboard sound or change its volume.

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": {
      "sound": "<sound>"
    },
    "name": "update_soundboard_sound"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
guildNoGuild (server) name or ID. Omit to use the default guild.
soundYesSound name or ID.
volumeNo

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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say whether name and volume are applied independently (partial update), whether omitting one leaves it unchanged, whether permissions such as manage-server are required, or what happens to existing references when a sound is renamed.

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?

A single short sentence with the two mutating actions front-loaded and no wasted words. Nothing is buried or padded.

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

Completeness2/5

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

For a mutation tool with four parameters, no output schema, and only half the parameters described in-schema, the description should do more: clarify partial-update semantics, permission requirements, and the effect of renaming. As written, an agent can guess the intent but not the operational details.

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?

With 50% schema description coverage, the description does add a useful framing: the tool's two mutating parameters are name and volume, while sound (required) and guild are targeting identifiers. That helps an agent understand the required parameter's role. However, it gives no format or constraint detail beyond the schema, and the guild default behavior is only documented in the schema.

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 specific verbs (rename, change volume) applied to a specific resource (soundboard sound), so an agent immediately knows this is the mutation path for an existing sound. It does not explicitly contrast with create_soundboard_sound or delete_soundboard_sound, but the mutating verbs make the distinction reasonably evident.

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 prerequisite (e.g. required permissions), and no mention of when a different tool should be used instead. The only implicit signal is that the operation applies to an existing sound, which the agent must infer.

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