Skip to main content
Glama
PaSympa

discord-mcp

by PaSympa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_create_invite

Create a Discord channel invite link with optional expiration, use limits, and temporary membership controls. Returns the invite URL and code for sharing access.

Instructions

Create an invite link for a channel, optionally limiting its lifetime, uses, and membership type. SECURITY: anyone with the returned link can join the server. Requires the Create Instant Invite permission. Returns the invite URL and code.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uniqueNoIf true, always mint a fresh invite instead of reusing an equivalent existing one. Default false.
max_ageNoInvite lifetime in seconds, 0–604800 (7 days); 0 means it never expires. Default 86400 (24h).
max_usesNoMaximum number of uses, 0–100; 0 means unlimited. Default 0.
temporaryNoIf true, members who join via this invite are removed when they disconnect (unless they get a role). Default false.
channel_idYesID (snowflake) of the channel the invite leads to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed11 schema fields changedv2.0.0
    • addedInput schema / properties / channel_id / pattern
      Added value: +"^\\d{17,20}$"
    • addedInput schema / properties / max_age / default
      Added value: +86400
    • changedInput schema / properties / max_age / description
      Previous value: -"Invite lifetime in seconds; 0 means it never expires. Default 86400 (24h)."New value: +"Invite lifetime in seconds, 0–604800 (7 days); 0 means it never expires. Default 86400 (24h)."
    • addedInput schema / properties / max_age / maximum
      Added value: +604800
    • addedInput schema / properties / max_age / minimum
      Added value: +0
    • changedInput schema / properties / max_age / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / max_uses / default
      Added value: +0
    • changedInput schema / properties / max_uses / description
      Previous value: -"Maximum number of uses; 0 means unlimited. Default 0."New value: +"Maximum number of uses, 0–100; 0 means unlimited. Default 0."
    • addedInput schema / properties / max_uses / maximum
      Added value: +100
    • addedInput schema / properties / max_uses / minimum
      Added value: +0
    • changedInput schema / properties / max_uses / type
      Previous value: -"number"New value: +"integer"
  3. Changed5 schema fields changedv1.6.0
    • addedInput schema / properties / channel_id / description
      Added value: +"ID (snowflake) of the channel the invite leads to."
    • changedInput schema / properties / max_age / description
      Previous value: -"Invite duration in seconds (0 = never expires). Default 86400 (24h)."New value: +"Invite lifetime in seconds; 0 means it never expires. Default 86400 (24h)."
    • changedInput schema / properties / max_uses / description
      Previous value: -"Max number of uses (0 = unlimited). Default 0."New value: +"Maximum number of uses; 0 means unlimited. Default 0."
    • changedInput schema / properties / temporary / description
      Previous value: -"If true, members joined via this invite are kicked when they disconnect. Default false."New value: +"If true, members who join via this invite are removed when they disconnect (unless they get a role). Default false."
    • changedInput schema / properties / unique / description
      Previous value: -"If true, create a new unique invite even if one exists. Default false."New value: +"If true, always mint a fresh invite instead of reusing an equivalent existing one. Default false."
  4. Addedv1.5.0

TDQS

A4.5/5.0
Behavior5/5

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

The description adds valuable behavioral context beyond the annotations: a security warning that anyone with the returned link can join the server, the required 'Create Instant Invite' permission, and the return payload. This goes well beyond the readOnlyHint/idempotentHint/destructiveHint flags and helps the agent anticipate side effects and failure conditions.

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?

Three sentences with no filler: purpose, security caveat, permission requirement, and return value are all stated efficiently. Important warnings are front-loaded and every sentence adds information an agent needs.

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

Completeness5/5

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

Despite having no output schema, the description covers the tool's purpose, key behavior, permission requirement, security implications, and return values. The remaining parameter details are fully documented in the input schema, so nothing essential is missing for correct invocation.

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 the schema already explains each parameter thoroughly. The description's summary of 'lifetime, uses, and membership type' maps loosely to max_age, max_uses, and temporary, but adds no extra detail beyond what the schema provides. Baseline 3 is appropriate.

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?

The description opens with a specific verb and resource: 'Create an invite link for a channel.' It clearly names the optional customization dimensions (lifetime, uses, membership type) and states what is returned (URL and code). This is enough to distinguish it from sibling tools like discord_create_event_invite.

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 communicates the clear context: invites are created for a channel, and the optional parameters control lifetime, uses, and membership type. It does not explicitly mention alternatives or say when not to use this tool, but the channel-focused wording implicitly separates it from event invites and DM tools.

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