Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_guild_vanity_invite

Read-only

Retrieve a Discord server's vanity invite URL by guild ID to share or manage its custom invite link.

Instructions

Get Guild Vanity Invite. [GET /guilds/{guild_id}/vanity-url]

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": "get_guild_vanity_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/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 nothing beyond the endpoint path — it does not say what is returned, that the guild must have a vanity URL configured, or what happens when none exists.

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?

It is short and front-loaded with the verb and resource, with zero wasted sentences. However, the brevity comes at the cost of under-specification — the second fragment is a raw HTTP route rather than agent-useful context.

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 simple single-parameter read tool with full annotation coverage and no output schema, the definition is minimally sufficient to invoke correctly. It is incomplete regarding what a vanity invite contains and error conditions, but those gaps are modest given the tool's simplicity.

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?

There is a single parameter with 100% schema description coverage ("Server (guild) ID"), so the schema already carries full meaning. The description adds no extra semantics beyond what the schema provides, which is the baseline case for a well-documented single parameter.

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

Purpose3/5

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

The description states a specific verb and resource ("Get Guild Vanity Invite") but is essentially a restatement of the tool name, adding only the raw endpoint path. The endpoint hint clarifies that this targets the guild's vanity URL rather than an arbitrary invite, but it does not explicitly distinguish this from siblings like get_invite or modify_guild_vanity_invite.

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 guidance on when to use this versus get_invite, create_invite, or modify_guild_vanity_invite, and no mention of prerequisites such as the VANITY_URL feature or Manage Guild permission. The only implicit cue is that the resource is guild-scoped via the path.

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