Skip to main content
Glama
scarecr0w12

discord-mcp

create_role

Create a new role in a Discord server by specifying name, color, permissions, and display options to organize members and manage access.

Instructions

Create a new role in a Discord server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guildIdYesThe ID of the server (guild)
nameYesName of the new role
colorNoHex color code (e.g., #FF0000)
hoistNoWhether to display the role separately
mentionableNoWhether the role can be mentioned
permissionsNoArray of permission names
positionNoPosition of the role
reasonNoReason for creating the role

Implementation Reference

  • The handler function for the 'create_role' tool. It fetches the Discord guild, constructs role creation options based on input parameters, creates the role using guild.roles.create(), handles errors with withErrorHandling, and returns the new role information or an error response.
    async ({ guildId, name, color, hoist, mentionable, permissions, position, reason }) => {
      const result = await withErrorHandling(async () => {
        const client = await getDiscordClient();
        const guild = await client.guilds.fetch(guildId);
    
        const roleOptions: Record<string, unknown> = { name };
        if (color !== undefined) roleOptions.color = color;
        if (hoist !== undefined) roleOptions.hoist = hoist;
        if (mentionable !== undefined) roleOptions.mentionable = mentionable;
        if (permissions !== undefined) {
          roleOptions.permissions = new PermissionsBitField(permissions as any);
        }
        if (position !== undefined) roleOptions.position = position;
        if (reason !== undefined) roleOptions.reason = reason;
    
        const newRole = await guild.roles.create(roleOptions);
        return {
          id: newRole.id,
          name: newRole.name,
          color: newRole.hexColor,
          position: newRole.position,
          message: 'Role created successfully',
        };
      });
    
      if (!result.success) {
        return { content: [{ type: 'text', text: result.error }], isError: true };
      }
    
      return { content: [{ type: 'text', text: JSON.stringify(result.data, null, 2) }] };
    }
  • Input schema for the 'create_role' tool defined using Zod, specifying parameters like guildId, name, optional color, permissions, etc.
    {
      guildId: z.string().describe('The ID of the server (guild)'),
      name: z.string().describe('Name of the new role'),
      color: z.string().optional().describe('Hex color code (e.g., #FF0000)'),
      hoist: z.boolean().optional().describe('Whether to display the role separately'),
      mentionable: z.boolean().optional().describe('Whether the role can be mentioned'),
      permissions: z.array(z.string()).optional().describe('Array of permission names'),
      position: z.number().optional().describe('Position of the role'),
      reason: z.string().optional().describe('Reason for creating the role'),
    },
  • The server.tool() call within registerRoleTools that registers the 'create_role' tool, providing name, description, input schema, and handler function.
    server.tool(
      'create_role',
      'Create a new role in a Discord server',
      {
        guildId: z.string().describe('The ID of the server (guild)'),
        name: z.string().describe('Name of the new role'),
        color: z.string().optional().describe('Hex color code (e.g., #FF0000)'),
        hoist: z.boolean().optional().describe('Whether to display the role separately'),
        mentionable: z.boolean().optional().describe('Whether the role can be mentioned'),
        permissions: z.array(z.string()).optional().describe('Array of permission names'),
        position: z.number().optional().describe('Position of the role'),
        reason: z.string().optional().describe('Reason for creating the role'),
      },
      async ({ guildId, name, color, hoist, mentionable, permissions, position, reason }) => {
        const result = await withErrorHandling(async () => {
          const client = await getDiscordClient();
          const guild = await client.guilds.fetch(guildId);
    
          const roleOptions: Record<string, unknown> = { name };
          if (color !== undefined) roleOptions.color = color;
          if (hoist !== undefined) roleOptions.hoist = hoist;
          if (mentionable !== undefined) roleOptions.mentionable = mentionable;
          if (permissions !== undefined) {
            roleOptions.permissions = new PermissionsBitField(permissions as any);
          }
          if (position !== undefined) roleOptions.position = position;
          if (reason !== undefined) roleOptions.reason = reason;
    
          const newRole = await guild.roles.create(roleOptions);
          return {
            id: newRole.id,
            name: newRole.name,
            color: newRole.hexColor,
            position: newRole.position,
            message: 'Role created successfully',
          };
        });
    
        if (!result.success) {
          return { content: [{ type: 'text', text: result.error }], isError: true };
        }
    
        return { content: [{ type: 'text', text: JSON.stringify(result.data, null, 2) }] };
      }
    );
  • src/index.ts:57-57 (registration)
    Invocation of registerRoleTools(server) in the main MCP server setup, which triggers the registration of the 'create_role' tool among others.
    registerRoleTools(server);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Create' implies a write operation, it doesn't address critical aspects like required permissions, rate limits, error conditions, or what happens on success (e.g., returns role ID). For a mutation tool with zero annotation coverage, this is a significant gap.

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?

The description is a single, efficient sentence that directly states the tool's purpose without any fluff or redundant information. It's appropriately sized and front-loaded, making it easy to understand at a glance.

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?

For a mutation tool with 8 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what the tool returns, error handling, permission requirements, or how it differs from related tools. The context signals indicate high complexity that isn't addressed in the description.

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?

The schema description coverage is 100%, with all 8 parameters well-documented in the schema itself. The description adds no parameter-specific information beyond what's already in the schema, so it meets the baseline of 3 where the schema does the heavy lifting.

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?

The description clearly states the action ('Create') and resource ('new role in a Discord server'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'modify_role' or 'delete_role', which would require explicit comparison for a score of 5.

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 like 'modify_role' or 'list_roles', nor does it mention prerequisites such as required permissions or server context. It simply states what the tool does without contextual usage information.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/scarecr0w12/discord-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server