Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_guild_profile

Updates a Discord server (guild) profile by guild ID and records an optional audit log reason for the change.

Instructions

Modify Guild Profile. [PATCH /guilds/{guild_id}/profile]

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_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the PATCH path is consistent with a mutation, so no contradiction. But the description adds nothing beyond that: it does not say which permissions are needed, whether omitted fields are preserved or cleared, what the returned profile looks like, or that a reason string is written to the audit log.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, but the second sentence is a bare HTTP route that duplicates information a schema-driven caller already needs and does not substitute for the missing content.

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 mutation tool with openWorldHint=true, no output schema, and a schema that exposes only guild_id and reason with no profile fields, the description leaves the critical question unanswered: how does the caller specify what to modify? Non-existent behavioral or payload context is a serious gap relative to the tool's complexity.

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 coverage is 100%, so both parameters (guild_id, reason) are fully documented in the schema, which sets the baseline at 3. The description only implies guild_id is a path parameter through the endpoint template and adds no meaning about what a profile modification payload would look like.

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

Purpose2/5

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

"Modify Guild Profile" restates the tool name nearly word for word, and the only additional content is the raw HTTP verb and path. It never says what a guild profile contains or which fields can be changed, so the agent cannot distinguish it from siblings like modify_guild or modify_guild_member_profile on purpose alone.

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 statement of when to use this tool, when not to, or which sibling handles adjacent cases (member profile vs user profile vs guild settings). The PATCH path is routing trivia, not usage guidance.

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