discord-mcp

discord_get_guild_info

Read-only

Fetches a Discord server's name, description, member, channel and role counts, boost tier, owner, and creation date using its guild ID.

Instructions

Get details about one server: name, description, member/channel/role counts, boost tier, owner, and creation date. The owner field is a user ID. roleCount includes the @everyone role. Use discord_get_server_stats for a finer breakdown (humans vs bots, channel types).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "guild_id": "<guild_id>"
    },
    "name": "discord_get_guild_info"
  }
}

Input Schema

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

Output Schema

Name	Required	Description	Default
`id`	Yes
`name`	Yes
`owner`	Yes
`createdAt`	Yes
`roleCount`	Yes
`boostCount`	Yes
`boostLevel`	Yes
`description`	Yes
`memberCount`	Yes
`channelCount`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.2.1Nov 7, 2026

removedOutput schema / properties / boostCount / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / boostCount / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / description / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / description / type
```
Added value: +[
+  "string",
+  "null"
+]
```

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": {
+    "boostCount": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "boostLevel": {
+      "type": "number"
+    },
+    "channelCount": {
+      "type": "number"
+    },
+    "createdAt": {
+      "type": "string"
+    },
+    "description": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "id": {
+      "type": "string"
+    },
+    "memberCount": {
+      "type": "number"
+    },
+    "name": {
+      "type": "string"
+    },
+    "owner": {
+      "type": "string"
+    },
+    "roleCount": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "description",
+    "memberCount",
+    "channelCount",
+    "roleCount",
+    "boostLevel",
+    "boostCount",
+    "createdAt",
+    "owner"
+  ],
+  "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
Removedv1.0.0May 1, 2026
First observedv0.1.0Mar 21, 2026

TDQS

A4.2/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, so safety is covered. The description adds real field-level semantics the annotations cannot: that owner is a raw user ID and that roleCount includes the @everyone role, both of which prevent miscounting mistakes. It does not mention rate limits or permission prerequisites, but for a read-only info call that is minor.

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?

Three short sentences: what it returns, then two caveats about field interpretation, then the sibling routing note last. Content is front-loaded and every clause carries information an agent could otherwise get wrong.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description does not need to explain return values, yet it still flags the two non-obvious field semantics that a schema alone would not convey. Combined with the explicit sibling alternative and full annotation coverage, an agent has enough to call this 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?

There is a single parameter, guild_id, and schema description coverage is 100% (it already states it is a Discord snowflake with a pattern). The description adds nothing about the parameter beyond the schema, which is the baseline expectation when coverage is complete.

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 ("Get details about one server") and then enumerates exactly which fields come back: name, description, member/channel/role counts, boost tier, owner, creation date. That level of specificity makes it immediately distinguishable from discord_list_guilds and from the many message/channel siblings.

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

Usage Guidelines4/5

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

It routes the agent away from itself when a finer breakdown is needed by naming discord_get_server_stats and the exact extra dimensions it provides (humans vs bots, channel types). It does not address when to prefer this over discord_list_guilds for discovery, so a small gap remains.

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

Deploy Server