Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_guild_join_requests

Read-only

List pending join requests for a Discord server to review membership applications and manage approvals. Filter by status and paginate with before/after IDs and limit.

Instructions

List Guild Join Requests. [GET /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>"
    },
    "name": "list_guild_join_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoReturn items after this ID (pagination)
limitNoMax results
beforeNoReturn items before this ID (pagination)
statusNoStatus
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context of its own — nothing about result ordering, pagination behavior, whether pending-only by default, permission requirements, or rate limits.

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?

It is two short tokens of text with zero waste and the resource is front-loaded. It is efficient, though the terseness borders on under-specification rather than deliberate brevity.

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?

For a paginated list tool with a status filter and no output schema, the description omits pagination semantics, default limits, ordering, and what the returned request objects contain. An agent would have to infer all of this from the schema alone.

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 five parameters (guild_id, after, before, limit, status) are already documented in the schema. The description adds no meaning beyond that baseline, which is acceptable but earns nothing extra.

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 description restates the tool name almost verbatim ("List Guild Join Requests") and adds only the raw HTTP endpoint. It does not distinguish this from close siblings such as list_user_guild_join_requests or get_guild_join_request, so an agent learns nothing beyond the name itself.

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 mention of alternatives (e.g., listing a single user's requests or fetching one request), and no stated prerequisites or scope conditions. The endpoint path is the only hint that this is guild-scoped.

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