discord-mcp

invites_create_channel

Generate a fresh Discord channel invite with custom expiration, max uses, or stream targeting. Returns invite code and metadata.

Instructions

Purpose: Create a new invite for a channel.

When to use:

Issue a fresh invite with custom expiry / use cap.
Generate a stream-target invite (target_type=1, target_user_id=…).

When NOT to use:

Reuse an existing invite → invites_list_channel then pick one.

Example: {channel_id:"112233445566778899", max_age:86400, max_uses:5, unique:true}

Returns: {code, expires_at, max_age, max_uses, temporary, unique, inviter_id}.

Input Schema

TableJSON Schema

Name	Required	Description
`unique`	No	Force a brand-new invite even if one with same parameters exists.
`max_age`	No	Seconds until expiry (0 = never). Default 86400.
`max_uses`	No	Max uses (0 = unlimited). Default 0.
`temporary`	No	If true, kicks members who do not get assigned a role. Default false.
`channel_id`	Yes	Channel to create the invite for
`target_type`	No	1 = STREAM, 2 = EMBEDDED_APPLICATION
`audit_reason`	No	Reason recorded in audit log (X-Audit-Log-Reason header)
`target_user_id`	No	User whose stream to target (target_type=1)
`target_application_id`	No	Embedded application to target (target_type=2)

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.28.0Sep 15, 2026

changedOutput schema / anyOf

Previous value: -[
-  {
-    "$schema": "https://json-schema.org/draft/2020-12/schema",
-    "additionalProperties": {},
-    "properties": {
-      "code": {
-        "description": "Discord invite code (base62, NOT a snowflake)",
-        "maxLength": 32,
-        "minLength": 1,
-        "type": "string"
-      },
-      "expires_at": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "inviter_id": {
-        "description": "Discord user ID",
-        "pattern": "^\\d{17,20}$",
-        "type": "string"
-      },
-      "max_age": {
-        "type": "number"
-      },
-      "max_uses": {
-        "type": "number"
-      },
-      "temporary": {
-        "type": "boolean"
-      },
-      "unique": {
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "code"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "category": {
-        "enum": [
-          "client",
-          "server"
-        ],
-        "type": "string"
-      },
-      "code": {
-        "type": "string"
-      },
-      "recovery_hint": {
-        "type": "string"
-      },
-      "retriable": {
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "code",
-      "retriable",
-      "category",
-      "recovery_hint"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "$schema": "https://json-schema.org/draft/2020-12/schema",
+    "additionalProperties": {},
+    "properties": {
+      "code": {
+        "description": "Discord invite code (base62, NOT a snowflake)",
+        "maxLength": 32,
+        "minLength": 1,
+        "type": "string"
+      },
+      "expires_at": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "inviter_id": {
+        "description": "Discord user ID",
+        "pattern": "^\\d{17,20}$",
+        "type": "string"
+      },
+      "max_age": {
+        "type": "number"
+      },
+      "max_uses": {
+        "type": "number"
+      },
+      "temporary": {
+        "type": "boolean"
+      },
+      "unique": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "code"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "category": {
+        "enum": [
+          "client",
+          "server"
+        ],
+        "type": "string"
+      },
+      "code": {
+        "type": "string"
+      },
+      "recovery_hint": {
+        "type": "string"
+      },
+      "retriable": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "code",
+      "retriable",
+      "category",
+      "recovery_hint"
+    ],
+    "type": "object"
+  }
+]

First observedv0.22.0Aug 14, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation profile is known. The description adds value by explaining the stream-target behavior (target_type=1) and the purpose of the unique flag in the example, plus the 'Returns' section provides expected output fields. It doesn't mention permission requirements or rate limits, but the annotation context and the creation-focused description sufficiently set expectations. No contradiction with annotations.

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?

The description is well-organized with markdown headers (Purpose, When to use, When NOT to use, Example, Returns), each section earning its place. It is concise, scannable, and front-loads the purpose and usage, making it easy for an agent to parse quickly.

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?

The description covers all essential aspects for correct selection and invocation: purpose, use cases, exclusions, an example with parameter values, and return fields. The output schema exists (as indicated) and annotations convey mutation/safety, so the description fully complements those structured signals. An agent has enough context to call this tool successfully.

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 fully documents all 9 parameters. The description adds only an example that uses 4 of them, illustrating a typical call but not adding semantic meaning beyond the schema. For a baseline of 3 when coverage is high, this 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 a new invite for a channel.' It further distinguishes itself from sibling tools by explicitly listing use cases (custom expiry/use cap, stream-target) and contrasting with invites_list_channel in the 'When NOT to use' section. This provides a clear identity that an agent can act on without inspecting sibling tool schemas.

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

Usage Guidelines5/5

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

The 'When to use' and 'When NOT to use' sections are explicit and actionable. They state exactly when to invoke this tool (issuing fresh invite, stream-target) and when to choose an alternative (reusing an existing invite → invites_list_channel). This is textbook usage guidance, leaving no ambiguity.

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

Deploy Server