Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_guild_soundboard_sound

Read-only

Fetch a specific soundboard sound from a Discord guild using its guild ID and sound ID to inspect or use that sound.

Instructions

Get Guild Soundboard Sound. [GET /guilds/{guild_id}/soundboard-sounds/{sound_id}]

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

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID
sound_idYesSoundboard sound ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, and the description adds nothing beyond that — the GET route merely restates the read nature already encoded in annotations. No mention of permissions needed, error behavior for invalid guild/sound IDs, or what the response contains. With annotations covering the safety profile, this is a passive description rather than an informative one.

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?

Extremely short and front-loaded with the resource name, with no filler text. Its brevity is not padding, although it borders on under-specification rather than economy.

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 simple two-parameter read the description is thin: with no output schema, the agent has no indication of the returned sound object's fields (name, volume, emoji, available flag, etc.) and no note on failure modes. It does not compensate for the missing return-value documentation.

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 description coverage is 100%, with both guild_id ('Server (guild) ID') and sound_id ('Soundboard sound ID') fully documented in the schema, so the baseline of 3 applies. The description adds no meaning beyond the schema — the route template merely echoes the two parameter names.

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 ('Get Guild Soundboard Sound') and adds only the raw HTTP route GET /guilds/{guild_id}/soundboard-sounds/{sound_id}. That route does confirm it fetches a single sound by guild and sound ID, but the actual semantics are almost entirely carried by the name itself rather than by explanatory prose.

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 instead of the closely related siblings such as get_soundboard_sound_guild, list_guild_soundboard_sounds, or list_default_soundboard_sounds. The agent must infer from the name alone that this returns one sound rather than a list or a default 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