discord-mcp

invites_list_channel

Read-onlyIdempotent

List active invites for a Discord channel, showing inviter, usage, and expiry to audit invite activity and identify candidates for cleanup.

Instructions

Purpose: List active invites for a single channel.

When to use:

Audit who created which invites and how often each is used.
Find candidates for invites_delete cleanup.

When NOT to use:

All invites across a guild → use guild_list_invites (Plan 7 Phase D).

Returns: {invites: [{code, uses, max_uses, max_age, expires_at, inviter_id, inviter_name, temporary}]}.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`channel_id`	Yes	Channel to list invites for

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": {
-      "invites": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "code": {
-              "description": "Discord invite code (base62, NOT a snowflake)",
-              "maxLength": 32,
-              "minLength": 1,
-              "type": "string"
-            },
-            "created_at": {
-              "type": "string"
-            },
-            "expires_at": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "inviter_id": {
-              "description": "Discord user ID",
-              "pattern": "^\\d{17,20}$",
-              "type": "string"
-            },
-            "inviter_name": {
-              "type": "string"
-            },
-            "max_age": {
-              "type": "number"
-            },
-            "max_uses": {
-              "type": "number"
-            },
-            "temporary": {
-              "type": "boolean"
-            },
-            "uses": {
-              "type": "number"
-            }
-          },
-          "required": [
-            "code"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      }
-    },
-    "required": [
-      "invites"
-    ],
-    "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": {
+      "invites": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "code": {
+              "description": "Discord invite code (base62, NOT a snowflake)",
+              "maxLength": 32,
+              "minLength": 1,
+              "type": "string"
+            },
+            "created_at": {
+              "type": "string"
+            },
+            "expires_at": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "inviter_id": {
+              "description": "Discord user ID",
+              "pattern": "^\\d{17,20}$",
+              "type": "string"
+            },
+            "inviter_name": {
+              "type": "string"
+            },
+            "max_age": {
+              "type": "number"
+            },
+            "max_uses": {
+              "type": "number"
+            },
+            "temporary": {
+              "type": "boolean"
+            },
+            "uses": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "code"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "invites"
+    ],
+    "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, idempotentHint, and destructiveHint=false, so the safety profile is clear. The description adds useful behavioral context by specifying 'active invites' and detailing the exact returned fields, which goes beyond what annotations alone provide.

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 compact and logically structured: purpose first, then usage guidance, exclusions, and return shape. Each section earns its place and there is no filler or redundancy.

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?

For a simple single-parameter read-only tool, this description is complete: purpose, usage, exclusions, return shape, and parameter are all covered. The annotations handle safety and idempotency, and the return format is explicitly documented.

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?

The input schema fully covers the single parameter channel_id with a clear description. The tool description does not add additional parameter semantics, but with 100% schema coverage, the baseline of 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: 'List active invites for a single channel.' It clearly distinguishes scope (single channel) from the sibling guild_list_invites and invites_get, so an agent can immediately tell what this tool does.

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 description gives explicit when-to-use scenarios (auditing invite creators/uses, finding cleanup candidates) and explicitly says when NOT to use it, naming the alternative guild_list_invites. This is exemplary routing guidance.

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

Deploy Server