discord-mcp

invites_get

Read-onlyIdempotent

Resolve a Discord invite code or URL to inspect its target guild and channel before sharing or deleting. Optionally include member counts and expiration.

Instructions

Purpose: Look up a Discord invite by its code (or full URL after stripping the prefix).

When to use:

Inspect an invite before deleting or sharing.
Resolve which guild/channel an invite points at.

When NOT to use:

Listing all invites for a channel → use invites_list_channel.

Example: {code:"abc123def", with_counts:true}

Returns: Projected invite shape with optional counts. Guild and channel names remain raw Discord data; untrusted_names provides a separately fenced copy.

Input Schema

TableJSON Schema

Name	Required	Description
`code`	Yes	Invite code (the bit after https://discord.gg/)
`with_counts`	No	Include approximate member/presence counts
`with_expiration`	No	Include expires_at field
`guild_scheduled_event_id`	No	Surface a specific scheduled event tied to the invite

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": {
-      "approximate_member_count": {
-        "type": "number"
-      },
-      "approximate_presence_count": {
-        "type": "number"
-      },
-      "channel_id": {
-        "anyOf": [
-          {
-            "description": "Discord channel ID (snowflake)",
-            "pattern": "^\\d{17,20}$",
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "code": {
-        "description": "Discord invite code (base62, NOT a snowflake)",
-        "maxLength": 32,
-        "minLength": 1,
-        "type": "string"
-      },
-      "expires_at": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "guild_id": {
-        "description": "Discord guild (server) ID",
-        "pattern": "^\\d{17,20}$",
-        "type": "string"
-      },
-      "inviter_id": {
-        "description": "Discord user ID",
-        "pattern": "^\\d{17,20}$",
-        "type": "string"
-      },
-      "inviter_name": {
-        "type": "string"
-      },
-      "untrusted_names": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "code",
-      "channel_id",
-      "untrusted_names"
-    ],
-    "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": {
+      "approximate_member_count": {
+        "type": "number"
+      },
+      "approximate_presence_count": {
+        "type": "number"
+      },
+      "channel_id": {
+        "anyOf": [
+          {
+            "description": "Discord channel ID (snowflake)",
+            "pattern": "^\\d{17,20}$",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "code": {
+        "description": "Discord invite code (base62, NOT a snowflake)",
+        "maxLength": 32,
+        "minLength": 1,
+        "type": "string"
+      },
+      "expires_at": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "guild_id": {
+        "description": "Discord guild (server) ID",
+        "pattern": "^\\d{17,20}$",
+        "type": "string"
+      },
+      "inviter_id": {
+        "description": "Discord user ID",
+        "pattern": "^\\d{17,20}$",
+        "type": "string"
+      },
+      "inviter_name": {
+        "type": "string"
+      },
+      "untrusted_names": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "code",
+      "channel_id",
+      "untrusted_names"
+    ],
+    "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.7/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent, and non-destructive behavior. The description adds value beyond those by explaining the return shape, noting that guild and channel names remain raw Discord data, and that untrusted_names provides a separately fenced copy. This is helpful behavioral context not available from annotations or schema alone.

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-structured with clear bolded sections: Purpose, When to use, When NOT to use, Example, and Returns. It is concise, front-loaded with the core purpose, and every sentence contributes meaningful information without 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?

The tool has an output schema, so return values are already defined externally. The description covers purpose, usage guidance, exclusions, an example, and notable output behavior like untrusted_names. For a lookup tool with read-only annotations and full schema coverage, nothing essential is missing.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds extra semantic value by clarifying that the code parameter can also accept a full URL after stripping the prefix, and by providing a concrete example showing code and with_counts usage. This goes beyond merely restating the schema.

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 states a specific verb and resource: 'Look up a Discord invite by its code'. It also clarifies that full URLs are accepted after stripping the prefix, and explicitly distinguishes itself from invites_list_channel. An agent can clearly 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 ('Inspect an invite before deleting or sharing', 'Resolve which guild/channel an invite points at') and an explicit when-not-to-use with the alternative tool named: 'Listing all invites for a channel → use invites_list_channel'. This is strong 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