Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

bulk_remove_relationships

Destructive

Remove multiple Discord relationships in one call, such as clearing incoming friend requests, with filters for relationship type or likely spammers.

Instructions

Remove many relationships at once (e.g. clear all incoming requests). [DELETE /users/@me/relationships]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bulk_remove_relationships"
  }
}

Input Schema

NameRequiredDescriptionDefault
filtersNofilters
relationship_typeNo3 incoming requests, 4 outgoing
only_likely_spammersNoonly likely spammers

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already disclose destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is covered. The description adds the concrete endpoint and a bulk-clear use case, but says nothing about irreversibility, whether partial failures are tolerated, auth requirements, or rate limits — meaningful gaps for a destructive bulk operation.

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?

A single front-loaded sentence states the action and scope, followed by a bracketed endpoint reference. Nothing is wasted and the most important information comes first.

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?

With three optional parameters and rich annotations, the description covers the essentials for calling the tool, and no output schema means return values need not be described. However, it omits what happens when filters is supplied versus omitted, and what a bulk destructive call leaves behind, which an agent would want for a high-impact operation.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3; the description slightly exceeds that by tying the tool's example to the incoming-requests type (relationship_type=3). It still leaves the ambiguous 'filters' array (numbers? user IDs?) unexplained, which is the one parameter the schema name does not really illuminate.

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 pairs a specific verb ('Remove') with a specific resource ('relationships') and a scope qualifier ('many at once'), so it is clearly distinguishable from the single-item siblings like remove_relationship and remove_friend. It does not explicitly name those siblings, which keeps it just short of a 5.

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?

The parenthetical 'e.g. clear all incoming requests' gives one concrete scenario, implicitly steering the agent toward relationship_type=3. There is no explicit when-not guidance or statement about choosing this over remove_relationship for individual removals, so usage is implied rather than spelled out.

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