Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_delete_invite

Revoke a Discord invite by its code, requiring Manage Server permission, to invalidate the link and prevent new members from joining.

Instructions

Revoke an invite by code. Requires Manage Server.

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": {
      "guildId": "<guildId>",
      "code": "<code>"
    },
    "name": "discord_delete_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesInvite code or trailing part of an invite URL
guildIdYesDiscord id (snowflake)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose the key permission requirement (Manage Server). However it never states that revocation is permanent/irreversible, what happens if the code is unknown or already revoked, or what is returned — meaningful gaps for a destructive operation with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two very short sentences with the action and identifier front-loaded and the prerequisite trailing. Nothing is padded or redundant.

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?

The tool is simple (2 required params, no nesting, no output schema) and the schema already explains both inputs, so the description covers the essentials. What it omits — irreversibility and error behavior on an invalid code — is exactly the context an agent would want before invoking a destructive call with no annotations.

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 both parameters (code with its URL-trailing-part semantics, guildId as snowflake) are already fully documented in the schema. The description's "by code" phrasing restates rather than extends that, so 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?

Names a specific verb and resource ("Revoke an invite") plus the identifier it acts on ("by code"), which is enough to separate it from discord_create_invite. It stops short of explicitly contrasting itself with any sibling, so it falls just under a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the agent must infer that this is the tool for removing an existing invite rather than creating one. The "Requires Manage Server" clause signals a prerequisite but is not framed as when/when-not guidance, and no alternative is named.

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