Skip to main content
Glama
wowjinxy
by wowjinxy

kick_member

Remove a user from a Discord server by specifying their user ID. This moderation tool helps manage server membership and enforce community rules.

Instructions

Kick a member from the server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes
server_idNo
reasonNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Implements the core logic to kick a Discord member from a guild using the Discord API, fetching the guild and member then calling member.kick()
    async def handle_kick_member(discord_client, arguments: Dict[str, Any]) -> List[TextContent]:
        """Kick a member from the server"""
        guild = await discord_client.fetch_guild(int(arguments["server_id"]))
        member = await guild.fetch_member(int(arguments["user_id"]))
        
        member_name = member.display_name
        await member.kick(reason=arguments.get("reason", "Kicked via MCP"))
        
        return [TextContent(
            type="text",
            text=f"Kicked member {member_name} from {guild.name}\nReason: {arguments.get('reason', 'Kicked via MCP')}"
        )]
  • Registers the 'kick_member' tool with the MCP server, defining its name, description, and input schema for server_id, user_id, and optional reason.
    Tool(
        name="kick_member",
        description="Kick a member from the server",
        inputSchema={
            "type": "object",
            "properties": {
                "server_id": {"type": "string", "description": "Server ID"},
                "user_id": {"type": "string", "description": "User ID to kick"},
                "reason": {"type": "string", "description": "Reason for kick"}
            },
            "required": ["server_id", "user_id"]
        }
    ),
  • Defines the input schema for the kick_member tool, specifying required server_id and user_id parameters with optional reason.
    inputSchema={
        "type": "object",
        "properties": {
            "server_id": {"type": "string", "description": "Server ID"},
            "user_id": {"type": "string", "description": "User ID to kick"},
            "reason": {"type": "string", "description": "Reason for kick"}
        },
        "required": ["server_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 full burden but only states the basic action. It doesn't disclose behavioral traits such as required permissions, whether the action is reversible, rate limits, or what the output contains. For a destructive moderation tool, this is a significant gap in transparency.

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, front-loading the core action. It's appropriately sized for the tool's purpose, though this conciseness comes at the cost of detail in other dimensions.

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 tool's complexity (destructive moderation action), lack of annotations, and 0% schema coverage, the description is incomplete. While an output schema exists, the description doesn't address critical context like permissions, consequences, or error handling, making it inadequate for safe 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 but adds no parameter information. It doesn't explain what 'user_id', 'server_id', or 'reason' mean, their formats, or usage context. With 3 parameters undocumented, this fails to provide necessary semantic clarity.

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 the server'), providing specific verb+resource. However, it doesn't explicitly differentiate from sibling tools like 'ban_member' or 'timeout_member', which serve related but distinct moderation purposes.

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_member' or 'timeout_member'. The description lacks context about prerequisites (e.g., permissions needed), exclusions, or typical use cases, leaving the agent with no usage direction.

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

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