Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

unmute_channel

Unmutes a Discord channel or DM by channel ID, restoring notifications and normal access to its messages.

Instructions

Unmute a channel or DM.

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

Input Schema

NameRequiredDescriptionDefault
channel_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world mutation, so the safety profile is covered. The description adds nothing beyond that: it does not say whether the unmute is per-user, whether it affects only notifications, what happens if the channel was never muted, or what the response contains. For a mutation tool the description should carry more.

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 zero filler and the action verb first. It is not padded, though its brevity is close to under-specification rather than disciplined conciseness.

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?

The tool is simple (one required parameter) and annotations cover the safety profile, so the description is minimally sufficient to identify and call it. It still leaves out what unmuting actually changes for the caller, which is the key semantic an agent needs when choosing between this and mute_channel.

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 description coverage is 0% for the single channel_id parameter, so the description must compensate and does so only partially. The phrase "channel or DM" usefully signals that either channel type's ID is accepted, but no ID format, snowflake vs. string, or validation behavior is given.

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 ("Unmute a channel") and adds the scope detail "or DM" that the name alone does not convey. It does not differentiate from the obvious inverse sibling mute_channel, but the action itself is unambiguous.

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 on when to use this versus mute_channel or other channel-state tools, and no prerequisites such as whether the caller must own the mute or be a member of the channel/DM. The agent must infer all usage context from the 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