discord-mcp

discord_get_invite

Read-only

Need to inspect a Discord invite? Look up any public invite code to see its target server, channel, inviter, and expiry.

Instructions

Look up a single invite by its code: target server and channel, inviter, and expiry. Works for any public invite, but this endpoint never returns usage counters (uses/max_uses/max_age read 0); use discord_list_invites or discord_list_channel_invites for real counters. Read-only. Returns a JSON object.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`invite_code`	Yes	The invite code, e.g. 'abc123'. A full discord.gg/abc123 URL is also accepted and stripped.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`code`	Yes
`uses`	Yes
`inviter`	Yes
`max_age`	Yes
`guild_id`	Yes
`max_uses`	Yes
`temporary`	Yes
`channel_id`	Yes
`created_at`	Yes
`expires_at`	Yes
`guild_name`	Yes
`channel_name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed1 schema field changedv2.0.0Jun 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "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"
+}

Changed1 schema field changedv1.6.0May 28, 2026

changedInput schema / properties / invite_code / description

Previous value: -"The invite code (e.g. 'abc123' from discord.gg/abc123)."New value: +"The invite code, e.g. 'abc123'. A full discord.gg/abc123 URL is also accepted and stripped."

Addedv1.5.0May 8, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses a non-obvious limitation: usage counters are never returned and read as 0. It also clarifies that the tool works on any public invite and returns JSON. No contradiction with annotations exists.

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?

Every sentence earns its place: purpose first, then the key limitation with alternatives, then read-only and return type. It is compact, front-loaded, and free of filler.

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 one-parameter, read-only lookup tool with an output schema, the description covers purpose, scope, known behavioral limitation, and alternative tools. Nothing needed to invoke it correctly is missing.

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 fully documents the single invite_code parameter, including URL stripping behavior. The description adds no additional parameter semantics beyond 'by its code,' so the baseline score 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: 'Look up a single invite by its code.' It also lists the returned data (target server/channel, inviter, expiry), making the scope unambiguous and distinct from invite-creation/deletion siblings.

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 explicitly tells agents when to use this tool ('Works for any public invite') and when not to use it ('never returns usage counters'), then names the alternatives: discord_list_invites or discord_list_channel_invites. This is direct 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