Skip to main content
Glama
Sign In
discord-mcp

discord-mcp

by founderie-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Invites (admin)

discord_admin_invites
Destructive

List active Discord server invite links with creator, use count, and expiry, or revoke an invite by code to control server access.

Instructions

List active invite links (who made them, uses, expiry), or revoke one by code. (Create with discord_admin_create_invite.)

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": {
      "action": "<action>"
    },
    "name": "discord_admin_invites"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNorevoke: invite code or URL
actionYes
reasonNoReason, recorded in Discord's audit log

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the agent knows revocation is a write with external effect. The description adds useful content detail about what list returns (creator, uses, expiry), which matters since there is no output schema. It stops short of stating that revocation is irreversible, whether elevated permissions are needed, or whether the list is paginated.

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 compact sentences with zero filler; the primary capability is front-loaded and the sibling cross-reference is tucked into a parenthetical rather than competing with the main clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter tool with no output schema, the definition covers purpose, the returned fields, and the alternative for creation. Remaining gaps (permissions required for revoke, pagination on list, irreversibility) are modest but real for a destructive 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 coverage is 67%: code and reason carry their own descriptions (including the audit-log note), while the action enum is undocumented in the schema. The description clarifies that code is used specifically for the revoke path, adding some meaning beyond the schema, but it does not explain the list/revoke choice or the effect of omitting code.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States two specific verbs (list, revoke) on a concrete resource (active invite links), and even enumerates the fields list returns (creator, uses, expiry). It is immediately distinguishable from discord_admin_create_invite, which it names as the tool for the opposite operation.

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

Usage Guidelines4/5

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

The description routes the creation case explicitly to discord_admin_create_invite, which is the most likely confusion given the sibling name. It does not spell out when to prefer revoke over other moderation paths (e.g. lockdown or bans), but the two supported actions are self-selecting via the required action enum.

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