Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

create_invite

Create a Discord channel invite link with configurable expiry, use limits, and temporary membership settings; defaults to 24 hours and unlimited uses.

Instructions

Create an invite link to a channel (defaults: 24h, unlimited uses).

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_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
uniqueNo
max_usesNo
temporaryNo
channel_idYes
max_age_secondsNo0 = never expires

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 this as a non-destructive write with open-world effects, so the safety profile is covered. The description adds the otherwise-undocumented behavior of what happens when optional parameters are omitted (24h expiry, unlimited uses), but says nothing about required permissions, rate limits, or whether existing invites are affected.

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?

A single front-loaded sentence with the resource named first and the defaults parenthesized at the end. Nothing is padding and no restatement of the tool name beyond what is needed to identify the scope.

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

Completeness2/5

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

For a mutation tool with five parameters, 20% schema coverage, and no output schema, the description is thin. It never says what the returned invite contains (code, URL, expiry), nor what unique and temporary control, leaving the agent to guess at half the inputs.

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 only 20% (just "0 = never expires"), so the description carries real weight here. It supplies defaults for max_age_seconds and max_uses, but leaves unique, temporary, and channel_id completely unexplained in both schema and description.

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") plus the scope target ("to a channel"), which distinguishes it from a user-invite or vanity-invite sibling. It stops short of explicitly naming a sibling to route away from, which keeps it below 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 Guidelines2/5

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

There is no when-to-use / when-not-to-use guidance at all. An agent must infer from the phrase "to a channel" that this is the channel-invite variant, with no stated prerequisites (e.g. required channel permissions) or alternatives.

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