Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_guild_member_profile

Edit your Discord server-specific profile by updating nickname, avatar, banner, bio, or pronouns. Use it to customize how you appear in a single guild without changing your global account.

Instructions

Edit your per-server profile (server avatar, banner, bio, pronouns). [PATCH /guilds/{guild_id}/profile/@me]

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": {
      "guild_id": "<guild_id>"
    },
    "name": "modify_guild_member_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
bioNo
nickNo
avatarNo
bannerNo
reasonNoReason (shown in the audit log)
guild_idYesServer (guild) ID
pronounsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 mutation and external-visibility semantics are covered. The description adds the concrete endpoint mapping and the editable field set, but says nothing about partial-update semantics (whether omitted fields are left untouched), the fact that null clears fields, audit-log side effects of 'reason', or what the call returns. That is modest added value beyond the 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?

One tight sentence with a front-loaded purpose, a parenthetical field summary, and the endpoint in brackets. No filler and nothing buried.

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?

With 7 parameters, no output schema, and a mutation that affects a publicly visible profile, the definition is adequate but thin: it does not clarify partial-update behavior, that only the caller's own profile can be modified, or permission requirements. The endpoint annotation plus field list covers the basics for an agent already familiar with the sibling family.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 29%, so the description must carry more weight, yet it merely re-lists four fields (avatar, banner, bio, pronouns) that the schema already documents with richer detail such as 'null removes it' and accepted image formats. It omits nick, reason, and guild_id entirely and adds no format or interaction guidance.

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 concrete verb and resource ('Edit your per-server profile') and scopes it with a field list (server avatar, banner, bio, pronouns) plus the REST endpoint PATCH /guilds/{guild_id}/profile/@me. The word 'your' and 'per-server' implicitly distinguish it from the sibling modify_guild_profile (server-wide) and modify_user_profile (global), though no sibling is named 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?

Usage is only implied: the '@me' endpoint and 'your per-server profile' signal that this edits the calling user's own membership profile in one guild. There is no explicit statement of when to prefer this over modify_user_profile or modify_guild_member, and no prerequisites or exclusions are given.

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