Skip to main content
Glama

discord_timeout_member

Temporarily restrict a Discord member's ability to interact by setting a timeout duration. Specify guild, user, and minutes to moderate server behavior.

Instructions

Put a member in timeout (0 minutes to remove the timeout).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guild_idYes
user_idYes
duration_minutesYes
reasonNo

Implementation Reference

  • The handler implementation for 'discord_timeout_member' that performs the timeout action on a Discord member.
    case "discord_timeout_member": {
      const guild = await discord.guilds.fetch(validateId(args.guild_id, "guild_id"));
      const member = await guild.members.fetch(args.user_id as string);
      const duration = args.duration_minutes as number;
      const until = duration > 0 ? new Date(Date.now() + duration * 60 * 1000) : null;
      await member.disableCommunicationUntil(until, args.reason as string | undefined);
      return {
        content: [{
          type: "text",
          text: duration > 0 ? `✅ ${member.user.tag} is in timeout for ${duration} minutes.` : `✅ Timeout removed from ${member.user.tag}.`,
        }],
      };
    }
  • The schema definition for the 'discord_timeout_member' tool.
      name: "discord_timeout_member",
      description: "Put a member in timeout (0 minutes to remove the timeout).",
      inputSchema: {
        type: "object",
        properties: {
          guild_id: { type: "string" },
          user_id: { type: "string" },
          duration_minutes: { type: "number" },
          reason: { type: "string" },
        },
        required: ["guild_id", "user_id", "duration_minutes"],
      },
    },
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 offers minimal behavioral insight. It mentions that 0 minutes removes timeout, hinting at dual functionality, but doesn't cover critical aspects like required permissions, rate limits, side effects, or what happens on success/failure. For a moderation tool with mutation, this is inadequate.

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 action and includes the important nuance about 0 minutes. It's appropriately sized and front-loaded with the core functionality.

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 (a moderation action with 4 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't address permissions, consequences, error conditions, or return values, leaving significant gaps for an agent to use it correctly.

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 details. It implies 'duration_minutes' accepts 0, but doesn't explain other parameters (guild_id, user_id, reason) or their formats. The description fails to provide meaningful semantics beyond what's inferred from the tool name.

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 ('Put a member in timeout') and resource ('member'), and specifies that 0 minutes removes the timeout, which adds useful nuance. However, it doesn't explicitly differentiate from sibling tools like discord_ban_member or discord_kick_member, which are related moderation actions.

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 like ban or kick, nor does it mention prerequisites (e.g., requiring moderator permissions) or contextual constraints. It only states what the tool does, not when to apply it.

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