Skip to main content
Glama
cappyeo

discord-mcp

by cappyeo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

users_modify_current

Idempotent

Update the authenticated Discord bot's profile: change its username, avatar, or banner. Use this to rename your bot or refresh its visual identity.

Instructions

Purpose: Update the authenticated bot/user profile (PATCH /users/@me).

When to use:

  • Rename the bot, change avatar/banner.

Note: User-scoped endpoint - does NOT accept audit_reason.

Returns: projected user shape {id, username, global_name, avatar, banner}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
avatarNoAvatar as base64 image data URI, or null to clear
bannerNoBanner as base64 image data URI, or null to clear
usernameNoNew username (2-32 chars)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.28.0
    • removedInput schema / properties / avatar / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / avatar / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedInput schema / properties / banner / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / banner / type
      Added value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / anyOf
      Previous value: -[
-  {
-    "$schema": "https://json-schema.org/draft/2020-12/schema",
-    "additionalProperties": {},
-    "properties": {
-      "avatar": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "banner": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "global_name": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "id": {
-        "description": "Discord user ID",
-        "pattern": "^\\d{17,20}$",
-        "type": "string"
-      },
-      "username": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "id",
-      "username",
-      "global_name",
-      "avatar",
-      "banner"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "category": {
-        "enum": [
-          "client",
-          "server"
-        ],
-        "type": "string"
-      },
-      "code": {
-        "type": "string"
-      },
-      "recovery_hint": {
-        "type": "string"
-      },
-      "retriable": {
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "code",
-      "retriable",
-      "category",
-      "recovery_hint"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "$schema": "https://json-schema.org/draft/2020-12/schema",
+    "additionalProperties": {},
+    "properties": {
+      "avatar": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "banner": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "global_name": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Discord user ID",
+        "pattern": "^\\d{17,20}$",
+        "type": "string"
+      },
+      "username": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "username",
+      "global_name",
+      "avatar",
+      "banner"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "category": {
+        "enum": [
+          "client",
+          "server"
+        ],
+        "type": "string"
+      },
+      "code": {
+        "type": "string"
+      },
+      "recovery_hint": {
+        "type": "string"
+      },
+      "retriable": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "code",
+      "retriable",
+      "category",
+      "recovery_hint"
+    ],
+    "type": "object"
+  }
+]
  2. First observedv0.22.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare not read-only, idempotent, and not destructive. The description adds genuine value beyond those: the user-scoped endpoint note ('does NOT accept audit_reason') and the projected return shape. No contradiction with annotations.

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?

Four terse labeled sections (Purpose, When to use, Note, Returns) with zero filler. The purpose is front-loaded, and every sentence earns its place, making the definition highly scannable for an agent.

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 mutation tool with 3 optional params, existing annotations, and an output schema, the description covers endpoint, scope, use cases, a parameter constraint, and return shape. Minor gap: it does not explicitly route the agent away from the similarly named members_modify_current sibling.

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%, so all three parameters are already documented (base64 data URI / null-to-clear, 2-32 chars). The description only echoes parameter intent in the 'When to use' section and adds no format or constraint detail beyond the schema, so baseline 3 applies.

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

Purpose5/5

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

Description states a specific verb ('Update') plus resource ('authenticated bot/user profile') and pins it to the exact endpoint (PATCH /users/@me). This clearly distinguishes it from siblings like users_get_current (read operation) and members_modify_current (guild member object, not user profile).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

A dedicated 'When to use' section lists concrete cases (rename the bot, change avatar/banner), giving an agent clear context for invoking this tool. However, it never names alternatives or provides when-not-to-use exclusions, leaving the boundary against members_modify_current to be inferred.

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