Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

delete_invite

Destructive

Revokes a Discord invite by code or full link, optionally recording a reason in the audit log. Use it to invalidate invite links and control server access.

Instructions

Revoke an invite. [DELETE /invites/{invite_code}]

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": {
      "invite_code": "<invite_code>"
    },
    "name": "delete_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
invite_codeYesInvite code or full invite link (discord.gg/xyz)

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 the safety profile is fully covered externally. The description adds nothing behavioral beyond that – no statement that revocation is permanent, that existing members are unaffected, or any auth/rate-limit context – leaving the endpoint path as its only extra information.

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 sentences with the action front-loaded and no padding. The bracketed REST path is mildly redundant but adds a useful mapping for engineers, so nothing is genuinely wasteful.

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 simple single-target destructive call, annotations cover the safety signal and the schema covers parameters fully, so the definition is callable as-is. It stops short of stating irreversibility or permission requirements, which are the main remaining questions for a delete operation.

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% and both parameters (invite_code, reason) are documented in the schema, including that a full invite link is accepted and that reason appears in the audit log. The description does not reference either parameter, so the schema does all the work; 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?

The description uses a specific verb ('Revoke') with a specific resource ('an invite') and the REST path DELETE /invites/{invite_code} confirms it is a deletion of a single invite by code. 'Revoke' naturally separates it from siblings like get_invite and create_invite, though it never names an alternative explicitly.

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 prerequisite or permission context, and no mention of what to do if the code is unknown or the invite already expired. The agent must infer everything from the verb alone.

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