Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

delete_user_connection

Destructive

Remove a linked third-party account from your Discord profile by specifying its connection type and account ID.

Instructions

Delete User Connection. [DELETE /users/@me/connections/{connection_type}/{connection_id}]

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": {
      "connection_type": "<connection_type>",
      "connection_id": "<connection_id>"
    },
    "name": "delete_user_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
connection_idYesConnection account ID
connection_typeYesConnection platform, e.g. github, spotify, steam, twitch, xbox, reddit, youtube

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 destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds only the HTTP route, and does not state that the deletion is irreversible, whether re-authentication is required, or what happens to linked data on the platform side.

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?

Two terse fragments with the resource named first and the endpoint second, no filler. It is efficient, though the terseness comes at the cost of the behavioral detail noted elsewhere.

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 destructive, open-world mutation with no output schema, the description should say more about consequences and error conditions (e.g. invalid connection_type, connection not found). It leaves the agent to infer all post-call behavior from the annotations alone.

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 coverage is 100%, with both connection_type and connection_id documented (including example platform values), so the schema carries the parameter burden. The description adds no format, case-sensitivity, or lookup guidance beyond that, which is the expected baseline.

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 names a specific verb and resource ('Delete User Connection') plus the exact endpoint DELETE /users/@me/connections/{connection_type}/{connection_id}, so the operation is unambiguous. It does not reference siblings such as modify_user_connection or refresh_user_connection, but the verb alone makes its role distinguishable.

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 guidance on when to use this versus modify_user_connection or refresh_user_connection, and no mention of prerequisites such as OAuth scopes or ownership. An agent gets the operation but no routing or precondition context.

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