Skip to main content
Glama

discord_set_member_permission

Modify individual member permissions for a Discord channel by allowing or denying specific access rights to control user interactions.

Instructions

Allow or deny specific permissions for a single member on a channel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYes
user_idYes
allowNo
denyNo
reasonNo

Implementation Reference

  • The handler logic for "discord_set_member_permission" which updates channel permission overwrites for a specific member using discord.js.
    case "discord_set_member_permission": {
      const channel = await getGuildChannel(args.channel_id as string);
      const options: PermissionOverwriteOptions = {};
      parsePermArray(args.allow).forEach((p) => { (options as Record<string, boolean>)[p] = true; });
      parsePermArray(args.deny).forEach((p) => { (options as Record<string, boolean>)[p] = false; });
      await channel.permissionOverwrites.edit(args.user_id as string, options, { reason: args.reason as string | undefined });
      return { content: [{ type: "text", text: `✅ Permissions updated for member ${args.user_id} on #${channel.name}.` }] };
    }
  • The tool definition schema for "discord_set_member_permission".
      name: "discord_set_member_permission",
      description: "Allow or deny specific permissions for a single member on a channel.",
      inputSchema: {
        type: "object",
        properties: {
          channel_id: { type: "string" },
          user_id: { type: "string" },
          allow: { type: "array", items: { type: "string" } },
          deny: { type: "array", items: { type: "string" } },
          reason: { type: "string" },
        },
        required: ["channel_id", "user_id"],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but lacks critical behavioral details. It doesn't mention required permissions (e.g., 'Manage Channel' permission), whether changes are reversible, rate limits, or what happens if both 'allow' and 'deny' arrays contain the same permission. The description only covers basic functionality without operational context.

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 with zero wasted words. It's appropriately front-loaded and doesn't contain unnecessary elaboration.

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 5 parameters, 0% schema coverage, no annotations, and no output schema, the description is inadequate. It lacks essential details about parameter usage, behavioral constraints, error conditions, and expected outcomes, leaving significant gaps for an agent to operate effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate but provides no parameter details. It doesn't explain what 'allow' and 'deny' arrays should contain (e.g., permission names like 'VIEW_CHANNEL'), format of 'channel_id' and 'user_id', or purpose of 'reason' field. The description adds no value beyond what's inferred from parameter names.

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 ('allow or deny specific permissions') and target ('for a single member on a channel'), which is specific and unambiguous. However, it doesn't differentiate from sibling tools like 'discord_set_role_permission' or 'discord_reset_channel_permissions', which handle similar permission management scenarios.

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 guidance is provided on when to use this tool versus alternatives like 'discord_set_role_permission' for role-based permissions or 'discord_reset_channel_permissions' for resetting permissions. The description only states what it does, not when it's appropriate.

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/PaSympa/discord-mcp'

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