Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

bulk_modify_guild_application_commands

Overwrite all guild-scoped Discord application commands for an app you own by replacing the existing set with a new command array in one request.

Instructions

Overwrite all guild commands of an app you own. [PUT /applications/{application_id}/guilds/{guild_id}/commands]

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": {
      "application_id": "<application_id>",
      "guild_id": "<guild_id>",
      "commands": "<commands>"
    },
    "name": "bulk_modify_guild_application_commands"
  }
}

Input Schema

NameRequiredDescriptionDefault
commandsYesArray body
guild_idYesServer (guild) ID
application_idYesApplication (app/bot) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true. The description adds the key behavioral fact that this is a full-set replacement ("Overwrite all"), which goes beyond the annotations -- useful, since an agent could otherwise assume it appends. However, it does not state that commands omitted from the array are removed, nor anything about failure/partial-apply semantics.

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?

Two short sentences: the operation first, the endpoint second. Front-loaded with zero filler. It is arguably too terse for a bulk mutation, but there is no wasted wording.

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 three-parameter bulk overwrite with no output schema, the description covers what the call does but omits the semantics an agent most needs: that existing commands not present in the array are replaced/removed, and what the command objects should contain.

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%, so all three parameters are documented in the schema and the baseline is 3. The description adds scope context (guild commands belonging to the app) but nothing about the shape or required fields of the commands array, whose item schema is an empty object.

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: "Overwrite all guild commands of an app you own," plus the underlying endpoint. The guild scope implicitly separates it from the global-command sibling, though no alternative is named explicitly.

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?

The only guidance is the ownership prerequisite ("an app you own"). Nothing says when to use this bulk overwrite versus modify_guild_application_command, create_guild_application_command, or the global counterpart, and no warning about replacing the entire command set.

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