Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_application_command_permissions

Updates Discord guild application command permissions to control which roles, users, or channels can view and use the command.

Instructions

Modify Application Command Permissions. [PUT /applications/{application_id}/guilds/{guild_id}/commands/{command_id}/permissions]

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>",
      "permissions": "<permissions>"
    },
    "name": "modify_application_command_permissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID
command_idYesApplication command ID
permissionsYesPermissions: bitfield string, or names like ["VIEW_CHANNEL","SEND_MESSAGES"]
application_idYesApplication (app/bot) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already convey an external, non-read-only, non-destructive operation. Beyond those, the description supplies only the PUT route and does not explain whether the supplied permissions replace existing entries, required authorization, side effects, or failure behavior.

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?

The definition is short, front-loaded, and easy to scan, with the endpoint providing compact scope information. However, the opening phrase largely repeats the tool name, and the raw endpoint is a substitute for more useful operational explanation.

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?

Together with the annotated schema, the definition is sufficient to identify the target and supply the required arguments. It remains incomplete for a permission mutation with no output schema because it gives no overwrite semantics, permission-entry details, prerequisites, or response expectations.

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 description coverage is 100%, so the baseline score of 3 applies. The path reinforces how the three IDs locate the command, but the description adds nothing about the permissions array's item structure or accepted values beyond the schema.

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?

The description gives a concrete verb and resource, and the PUT path narrows the target to one application's command within one guild. It does not explicitly contrast this with the get/list permission tools or modify_channel_permissions, so it stops short of strong sibling differentiation.

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 explicit statement of when to use this tool, what prerequisites apply, or when to choose a sibling such as get_application_command_permissions. The path implies the target scope, but that is not actionable selection guidance.

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