Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

create_channel_invite

Generate an invite link for a Discord channel and return its shareable discord.gg code, with controls for expiry, max uses, roles, and temporary access.

Instructions

Create an invite link for a channel. Returns the code (https://discord.gg/). [POST /channels/{channel_id}/invites]

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": "create_channel_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
flagsNoFlags bitfield
reasonNoReason (shown in the audit log)
uniqueNoAlways create a new invite instead of reusing a similar one
max_ageNoSeconds until the invite expires (0 = never, default 86400)
max_usesNoMax uses (0 = unlimited)
role_idsNoRole IDs
temporaryNoMembers joined through this invite are kicked when they disconnect unless given a role
channel_idYesChannel ID (text, voice, thread, forum or DM channel)
target_typeNoInvite target: 1 stream, 2 embedded application
target_user_idNoUser whose stream to show (target_type 1)
target_application_idNoEmbedded application ID (target_type 2)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false, openWorldHint=true, and readOnlyHint=false, so the mutation nature is covered. The description adds the return value format (https://discord.gg/<code>), which is real value, but omits permission requirements and Discord's invite-creation rate limits.

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: the purpose is front-loaded, then the return value, then the endpoint annotation in brackets. Nothing is padded, though the endpoint tag contributes little to an agent deciding how to call it.

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 description covers purpose and return value for an 11-parameter mutation tool with no output schema, and the schema handles the parameters. However, it omits preconditions an agent needs before invoking a write operation on a channel (permissions, whether invites are enabled, reuse behavior when unique is false).

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% across all 11 parameters, including defaults like max_age=86400 and the meaning of temporary and unique. The description adds no parameter meaning beyond the schema, 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 and resource ("Create an invite link for a channel") and includes the return shape and underlying endpoint. It scopes the tool to channel invites, which separates it from create_user_invite, but never explicitly contrasts itself with create_invite.

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, no mention of the alternatives in the sibling list, and no stated prerequisites (e.g., the CREATE_INSTANT_INVITE permission or channel invite settings). Usage is only implied by the name.

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