Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

delete_guild_integration

Destructive

Remove a Discord guild integration by guild ID and integration ID, optionally recording a reason in the audit log.

Instructions

Delete Guild Integration. [DELETE /guilds/{guild_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": {
      "guild_id": "<guild_id>",
      "integration_id": "<integration_id>"
    },
    "name": "delete_guild_integration"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
guild_idYesServer (guild) ID
integration_idYesIntegration 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 declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so safety is covered structurally. The description adds only the HTTP route; it says nothing about irreversibility, permission requirements, whether existing integration data/events are removed, or what a successful response looks like.

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 operation is stated first and the endpoint second. It is terse to the point of under-specification rather than verbose.

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?

A destructive mutation with full parameter documentation and explicit destructive annotations, so the essentials are covered. However, for an irreversible delete it omits permission requirements and side effects, leaving meaningful gaps.

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 guild_id, integration_id and the audit-log 'reason' are already explained in the schema. The description contributes no additional meaning about parameter formats or the audit-log effect, so the baseline 3 applies.

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?

States a specific verb+resource ('Delete Guild Integration') and reinforces it with the exact REST route, so the operation is unambiguous. The 'Guild' qualifier implicitly separates it from delete_channel_integration, but the description never explicitly names that distinction.

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 when-to-use or when-not-to-use guidance is given, and no prerequisites (e.g., required permissions such as MANAGE_GUILD) are stated. The agent must infer entirely from the name that this removes an integration from a specific guild.

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