Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_user_profile

Edit Discord profile details such as bio, pronouns, banner, accent color, and theme colors to update how your account appears.

Instructions

Edit your profile: bio, pronouns, banner, accent colour, profile theme colours. [PATCH /users/@me/profile]

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

Input Schema

NameRequiredDescriptionDefault
bioNo
bannerNo
pronounsNo
accent_colorNo
theme_colorsNo
profile_effect_idNo

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 mutation and externality profile is covered. The description adds the PATCH semantics and, via the banner param, that local paths/URLs/data URIs are accepted for uploads. It does not disclose partial-update behavior, whether nulls clear a field, or what the call returns — meaningful gaps for a PATCH tool.

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?

A single front-loaded sentence listing the editable fields, followed by the endpoint in brackets. Nothing is wasted, though a brief clause on partial updates would have earned its place.

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?

For a six-parameter, zero-required mutation tool with no output schema, the definition covers purpose and field scope but leaves the operationally important parts unstated: omitted-vs-null semantics, validation constraints, and response shape. Adequate to invoke, thin for confident use.

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 reported at 0%, so the description must carry the load; it does name five of the six parameters (bio, pronouns, banner, accent colour, theme colours) but omits profile_effect_id entirely. It also adds no format or clearing semantics (e.g. RGB integer encoding, theme color ordering, null-to-clear), so it only partially compensates.

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?

Names a specific verb (Edit) and resource (your profile) and enumerates the mutable fields: bio, pronouns, banner, accent colour, theme colours. It is clearly narrower than siblings like modify_current_user or modify_guild_profile, though it never names those alternatives explicitly.

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?

'your profile' plus the [PATCH /users/@me/profile] endpoint implies self-scoped edits only, which is useful routing context. However, there is no explicit when-to-use/when-not guidance versus modify_current_user or modify_guild_member_profile, and no stated prerequisites beyond the implied auth.

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