Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_create_invite

Create a Discord channel invite with optional max uses, expiry, temporary membership, uniqueness, and audit reason, so you can share controlled access links.

Instructions

Create an invite for a channel. Requires Create Invite.

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": {
      "channelId": "<channelId>"
    },
    "name": "discord_create_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
uniqueNo
maxUsesNo0 for unlimited
channelIdYesDiscord id (snowflake)
temporaryNoKick users who never got a role
maxAgeSecondsNo0 for never

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it only discloses the required permission ('Create Invite'). It does not say what gets returned (invite code/URL), that invites default to expiring in 86400 seconds, whether creation is idempotent, or what happens when the channel is not text/voice-capable — all material for a mutation tool.

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?

Two short sentences, permission constraint front-loaded right after the purpose, zero filler. Nothing is redundant.

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 six-parameter write tool with no annotations and no output schema, the description is too thin: the default expiry behaviour, the shape of the returned invite, and failure modes are unaddressed. An agent would have to infer most operational behaviour from the schema alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, so maxUses, maxAgeSeconds, temporary and channelId are already documented, but reason and unique have no descriptions and the tool description adds nothing to clarify them. No added meaning about defaults (unique=false, unlimited uses, 24h expiry) beyond what the schema states.

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 for a channel.' It is clearly distinguishable from discord_delete_invite and other create_* siblings by the resource named, though it makes no explicit sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

'Requires Create Invite' gives a prerequisite for calling it, which implies usage context, but there is no guidance on when to prefer this over alternatives or on common exclusions. It stops short of telling an agent the conditions under which invite creation is appropriate.

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