mcp-discord

discord_kick_user

Remove a user from a Discord server using their user ID and guild ID. The user can rejoin with an invite, and this action requires Kick Members permission.

Instructions

Remove a user from the guild. They can rejoin via invite. Requires Kick Members permission.

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>",
      "user_id": "<user_id>"
    },
    "name": "discord_kick_user"
  }
}

Input Schema

Name	Required	Description	Default
`guild_id`	Yes
`user_id`	Yes
`reason`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: the action is destructive (removal), has permission requirements, and mentions the user can rejoin via invite. It doesn't cover rate limits, error conditions, or response format, but provides essential context for a mutation operation.

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?

Two concise sentences with zero waste: first states the core action, second adds crucial context (rejoin possibility and permission requirement). Every word earns its place, and information is front-loaded appropriately.

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?

For a destructive mutation tool with 3 parameters, 0% schema coverage, and no output schema, the description provides good behavioral context but lacks parameter documentation and return value information. It's adequate for basic understanding but leaves gaps for proper implementation.

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 0%, so the description must compensate. It implies parameters (guild, user, reason through 'Remove a user') but doesn't explicitly name or explain them. The description adds some meaning about the action's purpose but doesn't fully document the 3 parameters beyond what's inferable from the tool name.

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 clearly states the specific action ('Remove a user from the guild') and resource ('user'), distinguishing it from siblings like discord_timeout_user (temporary restriction) or discord_remove_role (role removal). It uses precise terminology that matches Discord's API concepts.

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?

The description explicitly states when to use this tool ('Remove a user from the guild') and includes a prerequisite ('Requires Kick Members permission'). However, it doesn't explicitly contrast with alternatives like discord_timeout_user or explain when kicking vs. other moderation actions is appropriate.

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