Skip to main content
Glama
scarecr0w12

discord-mcp

list_bans

Retrieve a list of all banned users in a Discord server by providing the server ID to manage moderation actions and review server security.

Instructions

List all banned users in a server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guildIdYesThe ID of the server (guild)

Implementation Reference

  • Registration of the 'list_bans' tool using server.tool(). Includes inline input schema (guildId) and handler function that fetches all bans from the Discord guild using guild.bans.fetch(), maps them to {userId, username, reason}, handles errors with withErrorHandling, and returns JSON stringified response.
    // List bans
    server.tool(
      'list_bans',
      'List all banned users in a server',
      {
        guildId: z.string().describe('The ID of the server (guild)'),
      },
      async ({ guildId }) => {
        const result = await withErrorHandling(async () => {
          const client = await getDiscordClient();
          const guild = await client.guilds.fetch(guildId);
          const bans = await guild.bans.fetch();
    
          return bans.map((ban) => ({
            userId: ban.user.id,
            username: ban.user.username,
            reason: ban.reason,
          }));
        });
    
        if (!result.success) {
          return { content: [{ type: 'text', text: result.error }], isError: true };
        }
    
        return { content: [{ type: 'text', text: JSON.stringify(result.data, null, 2) }] };
      }
    );
  • Input schema for list_bans tool: requires guildId (string). Uses Zod for validation.
    {
      guildId: z.string().describe('The ID of the server (guild)'),
    },
  • Handler function for list_bans: fetches Discord client and guild, retrieves bans, formats output with userId, username, reason; wraps in withErrorHandling and returns MCP-formatted response.
    async ({ guildId }) => {
      const result = await withErrorHandling(async () => {
        const client = await getDiscordClient();
        const guild = await client.guilds.fetch(guildId);
        const bans = await guild.bans.fetch();
    
        return bans.map((ban) => ({
          userId: ban.user.id,
          username: ban.user.username,
          reason: ban.reason,
        }));
      });
    
      if (!result.success) {
        return { content: [{ type: 'text', text: result.error }], isError: true };
      }
    
      return { content: [{ type: 'text', text: JSON.stringify(result.data, null, 2) }] };
    }
  • src/index.ts:56-56 (registration)
    High-level registration call to registerMemberTools(server), which includes the list_bans tool among member management tools.
    registerMemberTools(server);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'List all banned users' implies a read-only operation, it doesn't specify critical details like permissions required, rate limits, pagination behavior, or output format. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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 a single, efficient sentence that directly states the tool's function without unnecessary words. It's front-loaded with the core action ('List all banned users'), making it easy to parse. Every word earns its place, with no redundancy or fluff.

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

Completeness3/5

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

Given the tool's low complexity (one parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks behavioral context (e.g., permissions, pagination) and usage guidelines. For a read operation in a server management context, more detail would help the agent use it effectively, but it's not completely inadequate.

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?

The input schema has 100% description coverage, with the single parameter 'guildId' clearly documented. The description doesn't add any parameter-specific information beyond what's in the schema, such as format examples or constraints. According to the rules, when schema coverage is high (>80%), the baseline score is 3 even without param details in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('List') and resource ('banned users in a server'), making the tool's purpose immediately understandable. It distinguishes itself from siblings like 'ban_member' or 'unban_member' by focusing on retrieval rather than modification. However, it doesn't explicitly differentiate from other list tools (e.g., 'list_members'), which prevents a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing server ID), exclusions, or compare it to similar tools like 'list_members' or 'get_audit_logs' for ban-related information. The agent must infer usage from the name and context alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/scarecr0w12/discord-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server