Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_guild_application_command

Update a Discord guild application command's name, description, options, permissions, or localization settings using its application, guild, and command IDs.

Instructions

Modify Guild Application Command. [PATCH /applications/{application_id}/guilds/{guild_id}/commands/{command_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": {
      "application_id": "<application_id>",
      "guild_id": "<guild_id>",
      "command_id": "<command_id>"
    },
    "name": "modify_guild_application_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName
nsfwNo
optionsNo
guild_idYesServer (guild) ID
command_idYesApplication command ID
descriptionNoDescription
application_idYesApplication (app/bot) ID
name_localizationsNo
description_localizationsNo
default_member_permissionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world operation. The description adds only the PATCH route, implying partial updates, but does not explain what happens to omitted fields, required permissions, or any side effects of modifying a guild command.

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 very short and front-loaded, but the bracketed endpoint duplicates structured/route information rather than adding useful semantic content. Every sentence is technically concise, yet the definition is undersized for a 10-parameter mutation tool.

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 complex mutation tool with many parameters and no output schema, the description is far too thin. It does not cover permission requirements, partial-update behavior, or any effects of the modification, leaving significant gaps for an agent to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 10 parameters and only 50% schema description coverage, the description provides no parameter-level meaning at all. Ambiguous fields such as 'options' and 'default_member_permissions' are not clarified, so it fails to compensate for the schema gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description essentially restates the tool name ('Modify Guild Application Command') and pairs it with a PATCH endpoint path. It does not explain what aspects of the command can be modified or how this differs from the sibling global command modifier.

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?

No guidance is given on when to use this tool versus modify_global_application_command or the bulk variants. The definition leaves the agent to infer the guild-scoped use case entirely from the tool name.

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