discord-server-mcp

create_invite

Generate a Discord channel invite link with limits on uses, expiry, and temporary membership. Use dry-run mode to preview requests before creating.

Instructions

Create an invite link to a channel.

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

Input Schema

Name	Required	Description
`bot`	No	Use this bot (name or id) instead of choosing automatically
`server`	No	Server name or id. Optional when the bot is in one server or DISCORD_GUILD_ID is set.
`unique`	No
`channel`	Yes	Channel name or id
`dry_run`	No	Show the requests that would be made without changing anything
`max_uses`	No	0 = unlimited
`temporary`	No	Kick members who leave without a role
`max_age_hours`	No	0 = never expires

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 12, 2026

TDQS

C2.9/5.0

Behavior2/5

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

The only annotation is readOnlyHint=false, so the description carries the burden for a mutation tool and adds almost nothing: no permission requirements, no statement that an invite is created immediately (and persists/grants access), and no indication that dry_run previews the requests. With 8 parameters and no output schema, the description should explain what state is altered and what the returned artifact is; it does not.

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?

A single front-loaded sentence with zero filler. It is not padded, though the brevity comes at the cost of the guidance noted above.

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 an 8-parameter mutation tool with no output schema, the definition should at least mention that it returns an invite URL and that invites grant channel access. Neither appears, leaving an agent to reconstruct the contract from the schema alone.

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 88%, so the schema already documents every parameter including the 0 = unlimited / 0 = never expires semantics and the dry_run behavior. The description adds no meaning beyond that, which is baseline 3 under the coverage rule.

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.' That is clear enough for an agent to know the effect. It does not, however, differentiate itself from the sibling bot_invite_link, so an agent browsing both must infer the distinction from the schemas.

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 guidance, no mention of the alternative bot_invite_link, and no prerequisite such as needing CREATE_INSTANT_INVITE permission in the target channel. Usage must be inferred entirely from the name.

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