Skip to main content
Glama
Oratorian

Discord MCP Server

by Oratorian

Kick Discord Member

discord_kick_member
Destructive

Remove a user from a Discord server by providing the server and user IDs. Optionally include a reason for the audit log.

Instructions

Kick a member from a Discord server.

Args:

  • guild_id (string): Discord server/guild ID

  • user_id (string): Discord user ID to kick

  • reason (string, optional): Reason for kick (visible in audit log)

Returns: Confirmation of kick

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNoReason for kick (visible in audit log)
user_idYesDiscord user ID (snowflake)
guild_idYesDiscord server/guild ID (snowflake)
Behavior3/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds that the reason is visible in the audit log, but doesn't elaborate on side effects like rejoin ability or permission requirements.

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?

Extremely concise: purpose, args list, and return value in six lines, front-loaded with the core action.

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?

Covers basic essentials: action, arguments, return type. Lacks permission hints or error conditions, but adequate for a simple destructive tool with complete schema and annotations.

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%, and the description merely restates the schema's parameter descriptions without adding new meaning or examples.

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 'Kick a member from a Discord server' with a specific verb and resource, distinguishing it from siblings like ban, remove role, or timeout.

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 on when to use this tool versus alternatives like discord_ban_member or discord_timeout_member; lacks context for selection.

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

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