Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

bulk_action_guild_join_requests

Bulk approve or reject pending Discord server join requests, optionally logging a reason in the audit log.

Instructions

Bulk Action Guild Join Requests. [PATCH /guilds/{guild_id}/requests]

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

Input Schema

NameRequiredDescriptionDefault
actionYesaction
reasonNoReason (shown in the audit log)
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond the endpoint path — no mention of required permissions, what happens to requests in each action, audit-log side effects, or rate limits, despite the reason parameter explicitly referencing the audit log.

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

Conciseness3/5

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

The text is very short with no wasted words, and the endpoint path is front-loaded alongside the name. However, its brevity comes from under-specification rather than tight writing, so it does little work per sentence.

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?

This is a mutating bulk operation with an unenumerated action parameter and no output schema. Given that complexity, the description should explain allowed actions and effects, but it only supplies a name and a route.

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 guild_id and reason are documented in the schema and the baseline applies. The description adds no detail for the critical action parameter, which has no enum and no documented allowed values, so it fails to compensate where it matters most.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The text largely restates the tool name ("Bulk Action Guild Join Requests") and appends a raw endpoint path. The PATCH /guilds/{guild_id}/requests path hints at modifying pending join requests, but no specific verb (approve, reject, etc.) or effect is stated, so an agent cannot tell precisely what the tool does.

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?

There is no when-to-use guidance, no prerequisites, and no routing to alternatives such as action_guild_join_request (single) or list_guild_join_requests. The only implicit signal is the word "Bulk", which suggests operating on multiple requests at once.

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