Skip to main content
Glama

discord_kick_member

Remove a member from a Discord server using guild and user IDs. Specify a reason for the moderation action when needed.

Instructions

Kick a member from a guild.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guild_idYes
user_idYes
reasonNo

Implementation Reference

  • The handler for the discord_kick_member tool, which fetches the guild member and kicks them using the discord.js library.
    case "discord_kick_member": {
      const guild = await discord.guilds.fetch(validateId(args.guild_id, "guild_id"));
      const member = await guild.members.fetch(args.user_id as string);
      await member.kick(args.reason as string | undefined);
      return { content: [{ type: "text", text: `✅ ${member.user.tag} has been kicked.` }] };
    }
  • The schema definition for the discord_kick_member tool, specifying input arguments.
      name: "discord_kick_member",
      description: "Kick a member from a guild.",
      inputSchema: {
        type: "object",
        properties: {
          guild_id: { type: "string" },
          user_id: { type: "string" },
          reason: { type: "string" },
        },
        required: ["guild_id", "user_id"],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions kicking a member but fails to explain critical details like required permissions (e.g., 'Kick Members'), whether the action is reversible, rate limits, or what happens after kicking (e.g., member can rejoin). This leaves significant gaps for an agent to understand the tool's behavior.

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 with zero waste—it directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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

Completeness2/5

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

Given the complexity of a destructive moderation action with no annotations, no output schema, and 3 undocumented parameters, the description is inadequate. It lacks essential context such as permissions, consequences, error handling, and how it differs from similar tools, making it incomplete for safe and effective use.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate by explaining parameters, but it adds no semantic information beyond what's inferred from the tool name. Parameters like 'guild_id', 'user_id', and 'reason' are undocumented in both schema and description, leaving their purpose and format unclear.

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 action ('Kick') and target ('a member from a guild'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'discord_ban_member' or 'discord_timeout_member', which are related moderation actions, leaving room for confusion about when to choose kick versus ban.

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?

No guidance is provided on when to use this tool versus alternatives like ban or timeout, nor does it mention prerequisites such as required permissions or guild context. The description only states what it does without indicating appropriate scenarios or constraints.

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/PaSympa/discord-mcp'

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