Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

search_guild_bans

Read-only

Search a Discord guild's ban list by username or user ID to identify banned users and support moderation reviews.

Instructions

Search the ban list by username. [GET /guilds/{guild_id}/bans/search]

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
queryNoSearch text
guild_idYesServer (guild) ID
user_idsNoUser IDs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only the REST route (GET /guilds/{guild_id}/bans/search), which is mildly useful context but says nothing about matching semantics (exact vs partial), pagination behavior, or whether the caller needs Manage Server permission.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short fragments with the capability front-loaded and no filler. The bracketed endpoint tag is low-value for an agent but compact and does convey the underlying API surface, so it does not seriously hurt readability.

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?

With annotations covering the read-only profile and full schema coverage, the basics are present, but for a search tool there is no mention of result shape (ban entries presumably include user and reason), paging via 'limit', or match behavior. Adequate but leaves real gaps an agent would hit at call time.

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%, so all four parameters are documented in the schema and baseline 3 applies. The description does not clarify the interaction between 'query' (free text) and 'user_ids' (explicit IDs) or how 'limit' behaves, and its 'by username' phrasing partially conflicts with the schema's broader 'Search text' field.

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?

States a specific verb and resource ("Search the ban list") plus the filtering axis ("by username"), which is enough to distinguish it from the sibling list_guild_bans. The narrowing is slightly off, though: the schema supports a free-text 'query' and 'user_ids', not just usernames, so the stated scope is narrower than reality.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the verb 'search' and the username filter — an agent can infer this is the targeted-lookup counterpart to listing all bans. There is no explicit when-to-use/when-not and no named alternative (e.g., list_guild_bans) for the unfiltered case.

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