Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

delete_channel_integration

Destructive

Remove an integration from a Discord channel by channel and integration ID, disconnecting linked apps or webhooks from that channel's settings.

Instructions

Delete Channel Integration. [DELETE /channels/{channel_id}/integrations/{integration_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": {
      "channel_id": "<channel_id>",
      "integration_id": "<integration_id>"
    },
    "name": "delete_channel_integration"
  }
}

Input Schema

NameRequiredDescriptionDefault
channel_idYesChannel ID (text, voice, thread, forum or DM channel)
integration_idYesIntegration ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is known without the description. The description adds nothing beyond the route, such as whether the deletion is immediate, irreversible, or requires Manage Channel permissions.

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 terse fragments with zero padding and the verb-resource front-loaded. It is efficiently sized, though efficiency here comes partly from saying very little.

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?

For a two-required-parameter destructive call, the annotations carry the risk profile and the schema carries parameter meaning, so the essentials are covered elsewhere. What is missing is the operational context an agent would want: effect on active integrations, required permissions, and the guild-level alternative.

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%, with channel_id explicitly documenting the channel types accepted and integration_id documented, so the baseline is 3. The description only mirrors the path template and adds no format or constraint detail beyond the schema.

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 restates the tool name and appends the HTTP route, which does pin down that the delete is scoped to one integration on one channel. However, it never distinguishes this from the closely named sibling delete_guild_integration, so the agent must infer the difference from the name alone.

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 stated prerequisites, and no mention of the channel-vs-guild variant that a sibling tool covers. The endpoint path is the only hint about applicability.

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