Skip to main content
Glama
Sign In
Discord Server Setup MCP

Discord Server Setup MCP

by cj-vana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_category

Create a new category in a Discord server to group related channels together. Configure name, position, and permission overwrites for access control.

Instructions

Creates a new category in a Discord server. Categories organize channels into groups.

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": {
      "name": "<name>"
    },
    "name": "create_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the category (1-100 characters)
guildIdNoGuild ID or name. Defaults to the currently selected guild.
positionNoPosition of the category in the channel list
permissionOverwritesNoPermission overwrites for roles/users. Use this to make the category private.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv2.0.1
    • addedInput schema / properties / guildId / description
      Added value: +"Guild ID or name. Defaults to the currently selected guild."
    • addedInput schema / properties / name / description
      Added value: +"Name of the category (1-100 characters)"
    • addedInput schema / properties / permissionOverwrites / description
      Added value: +"Permission overwrites for roles/users. Use this to make the category private."
    • changedInput schema / properties / permissionOverwrites / items / properties / allow / description
      Previous value: -"Permissions to allow"New value: +"Permission names to allow (SCREAMING_SNAKE_CASE)"
    • changedInput schema / properties / permissionOverwrites / items / properties / deny / description
      Previous value: -"Permissions to deny"New value: +"Permission names to deny (SCREAMING_SNAKE_CASE)"
    • changedInput schema / properties / permissionOverwrites / items / properties / id / description
      Previous value: -"Role ID or user ID"New value: +"Role ID or user ID this overwrite applies to"
    • changedInput schema / properties / permissionOverwrites / items / properties / type / description
      Previous value: -"Whether this is a role or user override"New value: +"Whether id refers to a role or a member"
    • addedInput schema / properties / position / description
      Added value: +"Position of the category in the channel list"
  2. First observedv2.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It only states the creation action and general purpose, without disclosing side effects, required permissions, rate limits, or failure modes. Critical behavioral aspects are omitted.

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?

Two sentences, no unnecessary words. Front-loaded with the core action and purpose. Every sentence serves a clear function.

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 output schema, 4 parameters, and no annotations, the description is too sparse. It lacks information about return values, error scenarios, prerequisite conditions, or the impact of parameters like 'position' and 'permissionOverwrites'. A more complete description would significantly aid an agent.

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%, so the description need not re-list parameters. However, it adds no additional context about parameter usage, formatting, or defaults beyond what the schema already provides. Baseline score of 3 is appropriate.

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

Purpose5/5

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

The description clearly states the verb ('creates'), resource ('category'), and context ('Discord server'), with an explanation of the concept ('organize channels into groups'). It distinguishes from siblings like 'create_channel' by specifying it is for categories rather than channels.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., 'create_channel' for channels, 'create_role' for roles). No context on when not to use it or what prerequisites exist.

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