discord-mcp

discord_list_guilds

Read-onlyIdempotent

List every Discord server (guild) the bot has joined to find a guild_id, returning names and IDs as Markdown or structured JSON.

Instructions

List every server (guild) the bot has been invited to.

A bot only sees servers where someone with Manage Server added it — it cannot browse
servers it isn't in. Use this to find a guild_id.

Returns: Markdown table of name and ID, or JSON list of {id, name, owner, permissions}
where `owner` means the bot's owner owns the server.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`response_format`	No	'markdown' for reading, 'json' for full structured data.	markdown

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 3, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/openWorld safety, but the description adds real behavioral context: the bot only sees guilds where someone with Manage Server added it, and it cannot browse outside its memberships. That permission/visibility constraint is not derivable from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose, then a useful visibility caveat, then usage guidance and returns. Slightly padded by a returns block that duplicates the output schema, but no sentence is wasteful enough to break flow.

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?

An output schema exists, so return values need not be restated, yet the description goes further by clarifying that `owner` means the bot's owner owns the server — non-obvious interpretation help. Combined with annotations covering safety, the agent has everything needed to call 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%, so the single response_format parameter is fully documented by the schema itself. The description's 'Markdown table ... or JSON list' phrasing mirrors the schema's markdown/json enum without adding syntax or constraint details, so the baseline 3 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?

States a specific verb and resource ('List every server (guild) the bot has been invited to') with clear scope. The 'bot has been invited to' qualifier implicitly distinguishes it from discord_get_guild, which fetches one guild by ID.

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?

Explicitly says 'Use this to find a guild_id', giving a clear reason to invoke the tool. It does not name a specific alternative (e.g., discord_get_guild) or an explicit when-not condition, so it stops short of a 5.

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