Skip to main content
Glama
Sign In
Discord MCP - Discord server management MCP for AI agents

Discord MCP - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update forum post

update_forum_post

Edit a Discord forum post's title or tags, pin or unpin it, lock or unlock replies, or archive it to manage thread visibility and discussion.

Instructions

Edit a post's title or tags, pin or unpin it within the forum, lock or unlock replies, or archive it.

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": {
      "post": "<post>"
    },
    "name": "update_forum_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
postYesPost title or thread ID.
tagsNoReplace the applied tags with these.
guildNoGuild (server) name or ID. Omit to use the default guild.
titleNo
lockedNo
pinnedNo
archivedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false and destructiveHint=false, so the agent knows this is a non-destructive mutation and the description carries a lighter burden. The description adds little beyond safety: it does not state whether archiving or locking is reversible, whether pinning requires elevated permissions, or what happens to omitted fields. It also does not warn that tag changes overwrite the existing tag set.

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?

A single sentence with the verb and resource front-loaded and the supported operations listed compactly. There is no filler, hedging, or repetition of the tool title.

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 7-parameter non-destructive mutation tool with annotations covering the safety profile and no output schema, the description gives an adequate operational picture. The remaining shortfall is permission requirements and the semantics of the guild parameter, which are minor but non-zero gaps.

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?

With 43% schema description coverage, the description must compensate, and it does map most parameters to user-visible actions (title, tags, pin/unpin, lock/unlock, archive). It leaves gaps: the guild parameter is never mentioned, and it does not clarify that tags replace rather than append, nor that booleans are absolute set-values rather than toggles.

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?

The description names a specific verb (edit) and resource (a post) and enumerates the exact mutations supported: title/tags, pin state, lock state, and archive state. That enumeration lets an agent distinguish this from sibling write tools like create_forum_post, delete_forum_post, or reply_to_forum_post without reading a schema.

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 implied rather than stated: it is clearly for modifying an existing post, and the listed operations hint at when each is appropriate. However, there is no explicit when-to-use versus alternatives guidance (e.g., use delete_forum_post to remove, or reply_to_forum_post to add content), and no prerequisites such as required permissions or moderation rights are mentioned.

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