Skip to main content
Glama
PaSympa

discord-mcp

by PaSympa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_update_forum_post

Idempotent

Update a Discord forum post by changing its title, locking or archiving it, or replacing its tags. Only specified fields are modified; set archived to close or reopen the post.

Instructions

Update a forum post's title, archived/locked state, or applied tags. Only provided fields change; passing applied_tags replaces the post's tags. Set archived:true to close a post without deleting it. Requires the Manage Threads permission.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoNew title/thread name (max 100 characters).
lockedNotrue to lock the post so only moderators can reply.
archivedNotrue to archive (close) the post, false to reopen it.
thread_idYesID (snowflake) of the forum post (thread) to update.
applied_tagsNoTag IDs to apply; replaces the post's current tags. Get valid IDs from discord_get_forum_tags.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed1 schema field changedv2.0.0
    • addedInput schema / properties / thread_id / pattern
      Added value: +"^\\d{17,20}$"
  3. Changed5 schema fields changedv1.6.0
    • changedInput schema / properties / applied_tags / description
      Previous value: -"Array of tag IDs to apply to the post."New value: +"Tag IDs to apply; replaces the post's current tags. Get valid IDs from discord_get_forum_tags."
    • changedInput schema / properties / archived / description
      Previous value: -"Whether to archive the thread."New value: +"true to archive (close) the post, false to reopen it."
    • changedInput schema / properties / locked / description
      Previous value: -"Whether to lock the thread."New value: +"true to lock the post so only moderators can reply."
    • addedInput schema / properties / thread_id / description
      Added value: +"ID (snowflake) of the forum post (thread) to update."
    • changedInput schema / properties / title / description
      Previous value: -"New title for the forum post."New value: +"New title/thread name (max 100 characters)."
  4. Addedv1.5.0
  5. Removedv1.0.0
  6. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, destructive=false, idempotent=true), the description adds the partial-update behavior, the replacement semantics of applied_tags, the non-deleting archive behavior, and a permission requirement. It does not cover error cases or rate limits, but it is solid for a mutation tool.

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?

Three sentences, no filler, with the core action front-loaded and the most critical behavioral caveats following in order. Every sentence carries information.

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 five-parameter tool with no output schema, the description covers the action, partial-update semantics, replacement behavior, non-deletion, and permission. It could be more complete by naming the alternative set_forum_tags tool or stating expected error outcomes, but the provided information is sufficient for a competent agent.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds object-level semantics not captured in the schema: only provided fields change and setting archived true closes without deleting. This partial-update nuance is genuinely useful for correct invocation.

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 specific action (update), a specific resource (forum post), and the affected fields (title, archived/locked state, applied tags). It is distinguishable from create/get/delete forum siblings, but it does not explicitly differentiate from the overlapping sibling discord_set_forum_tags.

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?

It gives useful context: only provided fields change, applied_tags replaces existing tags, archived:true closes without deletion, and Manage Threads permission is required. However, it never states when to prefer this tool over alternatives such as discord_set_forum_tags or when not to use it.

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