Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_guild_invites

Read-only

Retrieve all invite links for a Discord server by ID to audit or manage access; requires Manage Server permission.

Instructions

List all invites of a server (needs Manage Server). [GET /guilds/{guild_id}/invites]

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_invites"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 the Manage Server permission requirement, which is genuinely beyond the annotations, but says nothing about result size, pagination, or whether expired invites are included.

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?

One compact sentence with the permission caveat attached inline and the endpoint reference bracketed at the end. Nothing is front-loaded incorrectly and no words are wasted.

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

Completeness4/5

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

For a one-parameter read tool with annotations and a fully described schema, the definition covers purpose, scope and the permission gate. The only material gap is that it does not characterize the returned invite objects or any pagination, which is a minor omission for a simple list call.

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% and the single parameter carries its own description ('Server (guild) ID'), so the schema does the heavy lifting. The description only reinforces the mapping via the '[GET /guilds/{guild_id}/invites]' path, adding no format or edge-case detail beyond it.

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 ('List all invites of a server') and scopes it to a server rather than a channel or user, which meaningfully separates it from siblings like list_channel_invites and list_user_invites. It stops short of explicitly naming those alternatives, so the discrimination is implied rather than stated.

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?

The parenthetical '(needs Manage Server)' gives a concrete prerequisite that helps an agent decide whether the call can succeed, which is real guidance. However, there is no explicit when-to-use versus alternatives (e.g. channel-level invite listing) and no statement of what happens on missing permission.

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