Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_user_connection

Updates settings for a linked Discord account connection by type and ID, including name, visibility, activity display, friend sync, and metadata visibility.

Instructions

Modify User Connection. [PATCH /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": "<name>",
      "show_activity": "<show_activity>",
      "friend_sync": "<friend_sync>",
      "metadata_visibility": "<metadata_visibility>",
      "visibility": "<visibility>"
    },
    "name": "modify_user_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName
visibilityYesvisibility
friend_syncYesfriend sync
connection_idYesConnection account ID
show_activityYesshow activity
connection_typeYesConnection platform, e.g. github, spotify, steam, twitch, xbox, reddit, youtube
metadata_visibilityYesmetadata visibility

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 safety profile is covered. The description contributes the PATCH endpoint, which signals a partial-update semantic and the '@me' scope, but it says nothing about permission requirements, whether an omitted field is cleared, or what error conditions occur if the connection does not exist.

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 short fragments with no filler, and the resource is front-loaded before the route. It is structurally clean but so terse that no supporting context is offered.

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 7-parameter mutation with no output schema, the description plus full schema coverage and annotations cover the essentials. The notable gap is that several schema descriptions are near-tautologies ('friend sync', 'visibility', 'show activity'), yet the description does not compensate for those ambiguous flags.

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 the baseline is 3, and the path template names two of the required parameters (connection_type, connection_id) and their role as identifiers in the URL. That small addition lifts it slightly, though the ambiguous fields (friend_sync, show_activity, metadata_visibility) get no extra explanation.

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 ('Modify') and resource ('User Connection') and adds the HTTP route PATCH /users/@me/connections/{connection_type}/{connection_id}, which clarifies that this edits one of the authenticated user's linked third-party accounts. It does not distinguish the tool from siblings such as delete_user_connection or refresh_user_connection, so it stops 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 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 tool versus the delete, refresh, or list connection siblings, nor any stated prerequisites (e.g., a connection must already exist, OAuth scope requirements). The only implied usage comes from the verb 'Modify' and the path template.

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