Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

create_user_invite

Generate a Discord friend invite link so anyone who uses it is added as your friend.

Instructions

Create a friend invite link (anyone using it becomes your friend). [POST /users/@me/invites]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_user_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoCode

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world operation, and the description adds the meaningful semantic that anyone redeeming the link becomes the caller's friend. It does not disclose whether the invite expires, whether it can be revoked (delete_invite exists as a sibling), or what permissions are required to create one.

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?

A single front-loaded sentence states the action and its outcome, followed by a compact endpoint tag. Nothing is redundant or padded.

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?

For a zero-required-parameter creation tool with no output schema, the description covers the core effect but omits return shape (does it return the invite code/URL?), expiry, and revocability. Those gaps are not covered by annotations, which only address safety hints.

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 optional "code" parameter is documented in the schema, so the baseline of 3 applies. The description adds no meaning about what the code is for (custom vanity code vs. auto-generated) or how it interacts with the generated link.

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?

"Create a friend invite link" gives a specific verb and a scoped resource, and the parenthetical "anyone using it becomes your friend" establishes the effect, which distinguishes it from channel or guild invites among the siblings. It stops short of naming the sibling alternatives directly, so an agent must infer the boundary rather than read it.

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?

No when-to-use or when-not-to-use guidance is present. With siblings like create_channel_invite and create_invite in the catalog, the description never states that this one produces a personal/friend invite rather than a server invite; that distinction is only implied by the word "friend."

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