Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

bulk_modify_global_application_commands

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

Instructions

Overwrite all global commands of an app you own. [PUT /applications/{application_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>",
      "commands": "<commands>"
    },
    "name": "bulk_modify_global_application_commands"
  }
}

Input Schema

NameRequiredDescriptionDefault
commandsYesArray body
application_idYesApplication (app/bot) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior1/5

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

The description says the tool "Overwrite[s] all global commands", i.e. the existing command set is replaced and any command not resubmitted is dropped — that is destructive by definition. The annotations declare destructiveHint=false, so the description actively contradicts the structured safety signal an agent relies on for confirmation gating. Nothing about rate limits, propagation delay, or rollback is disclosed either.

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, front-loaded sentences with no filler; the replacement semantics land first. The bracketed "[PUT /applications/{application_id}/commands]" is developer-facing route notation that adds little for an agent that already has the schema, keeping it from a 5.

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?

This is a bulk-overwrite mutation with no output schema and a conflicting destructive hint, yet the description never explains what happens to omitted commands, whether the call is idempotent, or what the response contains. For a full-replacement operation on application state, that leaves the agent under-informed about consequences.

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 application_id and commands are already documented (the latter only as "Array body"). The description's "all global commands" usefully clarifies that the array is a complete replacement set rather than an incremental patch, but it adds no detail on required command object fields or ordering.

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?

"Overwrite all global commands of an app" gives a specific verb (overwrite) and a precisely scoped resource (the app's global command set), which clearly separates it from modify_global_application_command (single) and bulk_modify_guild_application_commands (guild-scoped). It stops short of naming any sibling, so the differentiation comes from the adjective "global" and "all" rather than explicit routing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase "of an app you own" supplies a real precondition (bot ownership) that an agent must check before invoking. However, it never states when to prefer this full replacement over the single-command modify/create/delete siblings, leaving the choice implied by the word "bulk".

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