Skip to main content
Glama
Sign In
Discord Vencord MCP Bridge

Discord Vencord MCP Bridge

by clawdecode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

discord_create_invite

Create a Discord channel invite with configurable expiry, use limit, and temporary membership through the Discord Vencord MCP Bridge.

Instructions

Create an invite for a channel.

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

Input Schema

NameRequiredDescriptionDefault
max_ageNoDuration in seconds (0 = never, default: 86400).
max_usesNoMax number of uses (0 = unlimited).
temporaryNoGrant temporary membership.
channel_idNoTarget channel ID (defaults to active).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and it says nothing about required permissions, whether the call is idempotent, whether an invite code/URL is produced, or what happens when max_uses is exhausted. For a mutation tool that mints a shareable credential, this is a meaningful gap.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the terseness is achieved partly by omitting information rather than by tight editing.

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?

With no annotations and no output schema, the description should cover permissions, the returned invite code, and failure modes. None of that is present, so an agent cannot predict the result of the call beyond the bare action.

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%, with defaults and the 0-means-never/unlimited semantics already documented per parameter. The description adds no meaning beyond the schema, so the baseline 3 applies.

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 ('Create an invite') plus the target scope ('for a channel'), which is enough to separate it from discord_list_invites and discord_delete_invite. It stops short of explicitly naming those siblings or clarifying DM vs guild channel scope.

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 the other invite tools, no prerequisites (e.g. needing manage-channel permission), and no mention of how it relates to discord_create_dm for DM flows. The agent must infer everything from the tool name.

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