Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_guild_discovery_metadata

Update a Discord server's discovery metadata—such as description, keywords, category, social links, and publication status—to control how the server appears in Discovery.

Instructions

Modify Guild Discovery Metadata. [PATCH /guilds/{guild_id}/discovery-metadata]

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

Input Schema

NameRequiredDescriptionDefault
aboutNo
reasonNoReason (shown in the audit log)
guild_idYesServer (guild) ID
keywordsNo
is_publishedNo
social_linksNo
reasons_to_joinNo
primary_category_idNo
emoji_discoverability_enabledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.9/5.0
Behavior2/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 safety profile is covered. The description adds nothing on top of that: no mention of required permissions, whether omitted fields are left untouched or nulled, partial-update semantics, or the effect of publishing. For a PATCH mutation with nine optional fields, this is a meaningful gap.

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, with no filler sentences. However, the bracketed endpoint path is redundant metadata rather than useful guidance, and the brevity here reflects under-specification rather than disciplined concision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nine-parameter mutation with 22% schema documentation, no output schema and only generic annotations, the description leaves nearly everything unexplained: which fields are meaningfully settable, permission requirements, and update semantics. An agent cannot reliably invoke this tool from the definition alone.

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

Parameters1/5

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

Schema description coverage is only 22%, and the descriptions that exist are bare name restatements ('about', 'keywords', 'social links'). The tool description supplies no parameter meaning whatsoever, so the agent has no explanation for is_published, primary_category_id, emoji_discoverability_enabled, reasons_to_join, or how the optional array fields behave.

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?

The description is essentially the tool name restated in prose ('Modify Guild Discovery Metadata') plus the raw HTTP path. It conveys that this is a mutating operation on discovery metadata, but adds no specificity about which aspects of discovery metadata are configurable or how this differs from get_guild_discovery_metadata.

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 when-to-use or when-not-to-use guidance at all. The sibling list contains obvious complements (get_guild_discovery_metadata, add/remove_guild_discovery_subcategory, list_discovery_categories), but the description never routes the agent between them or states prerequisites.

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