Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

ignore_user

Hide a Discord user's messages without blocking them by supplying their user ID, so unwanted content no longer appears in view.

Instructions

Ignore a user (hide their messages without blocking). [PUT /users/@me/relationships/{user_id}/ignore]

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": "ignore_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesUser ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/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 agent knows this is a non-destructive write. The description adds genuine value by explaining what 'ignore' actually does (suppresses the user's messages rather than severing the relationship), consistent with destructiveHint=false. However, it never states reversibility (whether the ignore can be undone), permission requirements, or side effects on existing DMs.

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?

One short sentence plus a bracketed route, with the behavioral clarification front-loaded. Every clause earns its place except the raw HTTP path, which is mostly redundant metadata for an agent that already has the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, no-output-schema mutation, the definition covers what the tool does and what it does not do (block). The remaining gap is reversibility — nothing tells the agent whether the action can be undone or how to undo it — but the tool's overall simplicity keeps this from being a major deficiency.

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?

There is a single required parameter, and the schema documents it at 100% coverage with a description ('User ID'). The description adds no format, type, or sourcing hints (e.g. whether it is a snowflake vs. username), so it neither compensates for nor degrades the schema. Baseline 3 applies.

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 definition gives a specific verb and resource ('Ignore a user') and adds a clarifying gloss, 'hide their messages without blocking,' which operationally separates it from blocking-style siblings like block_user. It stops short of explicitly naming that sibling, but an agent can still tell what distinct effect this tool has.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the 'without blocking' clause hints that this is the softer alternative to block_user, but there is no explicit when-to-use, when-not-to-use, or named alternative. The endpoint path signals a one-way write on the current user's relationships, which is context but not guidance.

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