Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

refresh_user_connection

Refreshes a Discord user connection for a specified platform and connection ID, updating linked account data.

Instructions

Refresh User Connection. [POST /users/@me/connections/{connection_type}/{connection_id}/refresh]

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": "refresh_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.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, so the safety profile is covered. Beyond that, the description adds only the HTTP path; it does not disclose what the refresh actually does, whether it hits the third-party platform, whether it can revoke or invalidate the existing connection, or what is returned.

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?

It is a single, front-loaded line with no padding; the bracketed endpoint is mildly redundant for an agent but does confirm the resource path. Nothing is buried or verbose.

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 mutating, open-world action with no output schema, the description leaves the essential question unanswered: what the refresh does and what comes back. An agent cannot predict the side effects or the response shape from this definition.

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 description coverage is 100%, with connection_id and connection_type both documented and examples listed for the platform values. The description adds no meaning beyond the schema, so the baseline 3 applies.

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

Purpose3/5

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

The name-plus-repeat 'Refresh User Connection' gives a verb and resource, and the verb distinguishes it from modify_user_connection and delete_user_connection. However, 'refresh' is underspecified: it never says whether this re-fetches an OAuth token, re-syncs external profile data, or re-validates the link.

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 call this versus modify_user_connection or list_user_connections. The agent must infer that a broken or stale connection is the trigger, and no prerequisites are stated.

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