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

List soundboard sounds

list_soundboard_sounds
Read-only

Retrieves custom soundboard sounds from a Discord server, optionally for a specified guild or the default, so AI agents can inspect available sound effects before using them.

Instructions

Custom soundboard sounds in the server.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_soundboard_sounds"
  }
}

Input Schema

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

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
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's burden is lower. It adds only the qualifiers 'custom' (user-uploaded sounds, not built-in) and 'in the server' (guild-scoped), and says nothing about ordering, pagination, or whether an empty result is normal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is only six words with zero waste, but it is a fragment lacking a verb rather than a tightly structured sentence. Brevity here reflects under-specification more than disciplined concision.

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

Completeness4/5

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

For a one-parameter, read-only listing tool with full schema coverage and no output schema, the essentials are present and the annotations carry the safety profile. The remaining gap is minor: no hint of what the returned list contains beyond 'custom soundboard sounds.'

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 100% and the single guild parameter already documents 'name or ID' plus the omit-to-use-default behavior, so baseline 3 applies. The description does not add any meaning about the guild parameter beyond the schema.

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 is a bare noun phrase, 'Custom soundboard sounds in the server,' with no verb, so an agent must infer 'list' from the tool name. The resource scope (server-side custom soundboard sounds) is clear enough, but nothing distinguishes it from siblings such as list_emojis or list_stickers beyond the noun itself.

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 the related create/update/delete_soundboard_sound siblings, and no stated prerequisites or exclusions. The agent gets no help choosing between this and other listing tools.

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