Skip to main content
Glama
PaSympa

discord-mcp

by PaSympa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_prune_members

Destructive

Remove Discord members who have been inactive (no roles, not seen) for a set number of days. Preview the count with a dry run first, then re-run with dry_run disabled to permanently prune.

Instructions

Remove members who have been inactive (no roles, not seen) for a number of days. SAFE BY DEFAULT: dry_run is true unless explicitly set to false, so call it first to preview the count, then re-call with dry_run:false to actually remove them. Removal is irreversible (members must rejoin). Requires the Kick Members permission.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysYesInactivity threshold in days (1–30).
rolesNoOptional role IDs (snowflakes) to include; by default only members with no roles are counted.
reasonNoOptional reason recorded in the server audit log.
dry_runNoIf true (default), only returns the count that would be pruned without removing anyone. Set false to actually prune.
guild_idYesDiscord server (guild) ID (snowflake).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed6 schema fields changedv2.0.0
    • addedInput schema / properties / days / maximum
      Added value: +30
    • addedInput schema / properties / days / minimum
      Added value: +1
    • changedInput schema / properties / days / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / dry_run / default
      Added value: +true
    • addedInput schema / properties / guild_id / pattern
      Added value: +"^\\d{17,20}$"
    • addedInput schema / properties / roles / items / pattern
      Added value: +"^\\d{17,20}$"
  3. Changed5 schema fields changedv1.6.0
    • changedInput schema / properties / days / description
      Previous value: -"Number of days of inactivity (1–30)."New value: +"Inactivity threshold in days (1–30)."
    • changedInput schema / properties / dry_run / description
      Previous value: -"If true (default), only returns count without pruning."New value: +"If true (default), only returns the count that would be pruned without removing anyone. Set false to actually prune."
    • addedInput schema / properties / guild_id / description
      Added value: +"Discord server (guild) ID (snowflake)."
    • addedInput schema / properties / reason / description
      Added value: +"Optional reason recorded in the server audit log."
    • changedInput schema / properties / roles / description
      Previous value: -"Role IDs to include in the prune."New value: +"Optional role IDs (snowflakes) to include; by default only members with no roles are counted."
  4. Addedv1.5.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark destructiveHint=true, but the description adds valuable behavioral context beyond that: safe-by-default dry_run behavior, the preview-then-remove workflow, irreversibility of removal, and the required permission. This gives the agent a clear safety model for a destructive 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?

Three sentences, each carrying distinct information: the action, the safe dry-run workflow, and the irreversibility/permission caveats. There is no filler or repetition, and the most important safety guidance is front-loaded.

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

Completeness5/5

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

For a destructive bulk operation with no output schema, the description supplies everything an agent needs to invoke it safely: preview-first behavior, irreversibility, permission requirements, and the inactivity criteria. With full schema coverage, no critical operational detail is missing.

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 coverage is 100%, so the parameters are already fully documented. The description reinforces dry_run semantics and the inactivity criteria, but adds no new syntax or parameter details beyond what the input schema provides, which matches the baseline.

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 opens with a specific verb and target: 'Remove members who have been inactive (no roles, not seen) for a number of days.' This clearly states what the tool does and distinguishes it from individual member actions like kick or ban by focusing on bulk pruning of inactive members.

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 provides an explicit safe workflow: call with dry_run true to preview the count, then re-call with dry_run:false to actually remove. It also states the Kick Members permission prerequisite. It does not explicitly compare against alternative sibling tools, so it stops short of a 5.

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

Deploy Server

Other Tools