discord-mcp

Create invite (admin)

discord_admin_create_invite

Creates an invite link for a Discord channel with configurable expiry, use limit, and audit-log reason.

Instructions

Create an invite link to a channel. Defaults: expires in 24 hours, single use.

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>"
    },
    "name": "discord_admin_create_invite"
  }
}

Input Schema

Name	Required	Description
`reason`	No	Reason, recorded in Discord's audit log
`max_uses`	No	0 = unlimited
`channel_id`	Yes	Channel the invite lands in
`expires_hours`	No	0 = never expires

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 12, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare this is a non-read-only, open-world, non-destructive write. The description adds the key behavioral fact that a public link is produced with short expiry and single use by default, but omits permission requirements and whether the returned link is reusable/revocable.

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, action first, defaults second. Minimal waste, though the defaults sentence largely duplicates structured schema data.

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 simple, single-required-parameter tool with full schema coverage, so the description is adequate. It still leaves the output (invite code/URL) and required permissions implicit, which matters for an open-world invite creation call.

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 100%, with defaults, ranges, and '0 = unlimited/never expires' semantics all documented inline. The description only echoes the default values already present in the schema, adding no new parameter meaning.

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 and resource: 'Create an invite link to a channel.' The agent can tell it apart from channel/role creation siblings, though it does not distinguish itself from discord_admin_invites, which plausibly overlaps on invite management.

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, and no named alternative. The only guidance is a restatement of defaults, which an agent would still have to infer apply automatically.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server