Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_application

Update a Discord application's settings via PATCH, including name, description, icons, tags, redirect and webhook URLs. Use it to change app configuration without recreating it.

Instructions

Modify Application. [PATCH /applications/{application_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>",
      "role_connections_verification_url": "<role_connections_verification_url>"
    },
    "name": "modify_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNo
nameNoName
tagsNo
flagsNoFlags bitfield
guild_idNo
cover_imageNo
descriptionNo
rpc_originsNo
deeplink_uriNo
developer_idsNo
publisher_idsNo
redirect_urisNo
application_idYesApplication (app/bot) ID
install_paramsNo
max_participantsNo
custom_install_urlNo
event_webhooks_urlNoevent webhooks url
integration_publicNointegration public
monetization_stateNomonetization state
privacy_policy_urlNo
event_webhooks_typesNoevent webhooks types
interactions_versionNointeractions version
terms_of_service_urlNo
discoverability_stateNodiscoverability state
event_webhooks_statusNoevent webhooks status
explicit_content_filterNoMedia filter: 0 off, 1 members without roles, 2 everyone
integration_types_configNointegration types config
interactions_event_typesNo
connection_entrypoint_urlNoconnection entrypoint url
interactions_endpoint_urlNointeractions endpoint url
integration_require_code_grantNointegration require code grant
role_connections_verification_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare this as a non-read-only, open-world, non-destructive operation. The description adds the PATCH method, which usefully implies a partial update, but it does not explain required permissions, which fields remain unchanged, or side effects of an open-world modification.

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 description is tightly front-loaded into two fragments with no wasted wording. It is concise and clear, though the terse format does little to scaffold a complex payload.

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 32-parameter mutation with nested objects and no output schema, the definition gives almost no usable context. It does not explain required fields, partial-update semantics, or the scope of what can be changed, leaving the agent with an endpoint only.

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

Parameters1/5

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

The tool has 32 parameters and only 47% schema description coverage, so the description should compensate. Instead it mentions only the application_id path parameter and gives no meaning for the many optional fields or the required role_connections_verification_url.

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 states a specific verb and resource, 'Modify Application', and the endpoint path clarifies the target as the application object. However, it does not explicitly distinguish this tool from siblings such as modify_application_emoji, modify_application_command_permissions, or the global/guild command modifiers.

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?

It implies use for updating an existing application but gives no guidance on when to choose this over get_application, create_application, or other modify_* tools. No prerequisites, permissions, or partial-update workflow are mentioned.

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