Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_global_application_command

Update a global Discord application command by ID through PATCH, changing its name, description, options, permissions, localizations, contexts, or integration types.

Instructions

Modify Global Application Command. [PATCH /applications/{application_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>",
      "command_id": "<command_id>",
      "default_member_permissions": "<default_member_permissions>"
    },
    "name": "modify_global_application_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName
nsfwNo
handlerNo
optionsNo
contextsNo
command_idYesApplication command ID
descriptionNoDescription
application_idYesApplication (app/bot) ID
integration_typesNo
name_localizationsNo
description_localizationsNo
default_member_permissionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the description's burden is lower, but it adds nothing beyond the endpoint. It does not say whether omitted fields are preserved (PATCH semantics), whether changes take effect immediately for users, what permissions are required, or what happens to existing commands.

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 fragments with zero filler. The terseness is not wasteful, though it leaves the definition under-specified, which is penalized in other dimensions rather than here.

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

Completeness1/5

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

For a 12-parameter mutation with one-third schema coverage, no output schema, and a required parameter (default_member_permissions) that is oddly nullable, the description supplies almost nothing. An agent cannot determine what fields are meaningfully updatable or what the call returns.

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?

Schema coverage is only 33% across 12 parameters, and several fields (handler, options, contexts, integration_types, name_localizations) are documented with nothing but their own name. The description adds no parameter meaning beyond the path template, which merely confirms application_id and command_id are path identifiers.

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 gives a verb (Modify) and a resource (Global Application Command), and 'global' implicitly separates it from the guild-scoped sibling. However, it essentially restates the tool name and appends the HTTP endpoint, without clarifying scope, what 'modify' means (full vs partial replacement), or how it differs from bulk_modify_global_application_commands.

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 prerequisites, and no routing to alternatives such as bulk_modify_global_application_commands or modify_guild_application_command. The only usage hint an agent can infer is from the name and the PATCH path.

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