Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

unblock_user

Unblock a Discord user by ID to restore direct messaging and interaction after they were previously blocked.

Instructions

Unblock a user.

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

Input Schema

NameRequiredDescriptionDefault
user_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is partly covered. The description adds nothing about what the unblock operation actually changes, whether it requires elevated permissions, or whether the affected user is notified - context the annotations cannot supply.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three words with zero padding and no awkward phrasing, but the brevity comes at the cost of substance rather than being disciplined concision. Nothing is front-loaded because there is nothing to load.

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?

This is a simple single-parameter mutation, so it needs little, but the definition still omits the ID format, permission requirements, and any side effects or return behavior. A one-word resource reference is not enough for an agent to call it safely in an unfamiliar guild context.

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?

The single parameter user_id has 0% schema description coverage, and the description only says 'a user' without clarifying whether this is a numeric ID, snowflake, or username, or where to obtain it. With low coverage the description must compensate, and it does not.

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

Purpose2/5

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

The description simply expands the tool name 'unblock_user' into 'Unblock a user,' adding no scope information. It does not say whether the unblock applies globally, per-guild, or per-context, so the agent learns nothing beyond what the name already conveys.

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 when-to-use guidance, no mention of prerequisites (such as the user currently being blocked), and no reference to alternatives like block_user or ignore_user. The inverse relationship to block_user is inferable from the names alone, not from the definition.

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