discord-mcp

discord_list_invites

Read-only

Retrieve every active invite across a Discord server, showing code, URL, channel, inviter, uses, and expiry. Read-only and requires Manage Server permission.

Instructions

List all active invites across a server (code, url, channel, inviter, uses, expiry). Requires the Manage Server permission. Read-only. Use discord_list_channel_invites to scope to one channel.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`guild_id`	Yes	Discord server (guild) ID (snowflake).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`invites`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.2.0Sep 6, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed2 schema fields changedv2.0.0Jun 27, 2026

addedInput schema / properties / guild_id / pattern
```
Added value: +"^\\d{17,20}$"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "invites": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "channel_id": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "channel_name": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "code": {
+            "type": "string"
+          },
+          "created_at": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "expires_at": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "guild_id": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "guild_name": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "inviter": {
+            "anyOf": [
+              {
+                "additionalProperties": false,
+                "properties": {
+                  "id": {
+                    "type": "string"
+                  },
+                  "username": {
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "id",
+                  "username"
+                ],
+                "type": "object"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "max_age": {
+            "type": "number"
+          },
+          "max_uses": {
+            "type": "number"
+          },
+          "temporary": {
+            "type": "boolean"
+          },
+          "url": {
+            "type": "string"
+          },
+          "uses": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "code",
+          "url",
+          "guild_id",
+          "guild_name",
+          "channel_id",
+          "channel_name",
+          "inviter",
+          "uses",
+          "max_uses",
+          "max_age",
+          "temporary",
+          "created_at",
+          "expires_at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "invites"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv1.6.0May 28, 2026
- addedInput schema / properties / guild_id / description
```
Added value: +"Discord server (guild) ID (snowflake)."
```
Addedv1.5.0May 8, 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=true and openWorldHint=true. The description adds useful behavioral context: the permission requirement, that only active invites are returned, and that 'all' invites across the server are included. This goes beyond the structured annotations without contradicting them.

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 two sentences with no filler. It front-loads the core action and scope, then adds permission, read-only status, and the alternative tool. Every sentence earns its place.

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?

This is a low-complexity single-parameter list tool with an output schema. The description covers the permission requirement, the scope, the returned fields, and the relevant sibling alternative. Nothing critical is missing for an agent to invoke it correctly.

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% and the only parameter, guild_id, is already clearly documented as a Discord server ID snowflake. The description adds no additional parameter-level meaning beyond what the schema provides, so the baseline score applies.

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 uses a specific verb ('List') and resource ('all active invites across a server'), lists the returned fields, and explicitly distinguishes itself from the sibling tool discord_list_channel_invites. This makes the tool's purpose immediately clear and unambiguous.

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 names the alternative discord_list_channel_invites and gives the exact condition for choosing it ('to scope to one channel'). It also states the required permission (Manage Server), giving clear guidance on when this tool 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