Skip to main content
Glama

discord_update_forum_post

Modify Discord forum posts by updating titles, tags, or changing archived and locked status for thread management.

Instructions

Update a forum post's title, archived/locked status, or applied tags.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
thread_idYes
titleNoNew title for the forum post.
archivedNoWhether to archive the thread.
lockedNoWhether to lock the thread.
applied_tagsNoArray of tag IDs to apply to the post.

Implementation Reference

  • The handler for "discord_update_forum_post" that edits the thread using thread.edit.
    case "discord_update_forum_post": {
      const thread = await getThreadChannel(args.thread_id as string);
      const editOptions: Record<string, unknown> = {};
      if (args.title !== undefined) editOptions.name = args.title as string;
      if (args.archived !== undefined) editOptions.archived = args.archived as boolean;
      if (args.locked !== undefined) editOptions.locked = args.locked as boolean;
      if (args.applied_tags !== undefined) editOptions.appliedTags = args.applied_tags as string[];
      await thread.edit(editOptions);
      return { content: [{ type: "text", text: `✅ Forum post "${thread.name}" updated.` }] };
    }
  • The MCP schema definition for the tool "discord_update_forum_post".
    {
      name: "discord_update_forum_post",
      description: "Update a forum post's title, archived/locked status, or applied tags.",
      inputSchema: {
        type: "object",
        properties: {
          thread_id: { type: "string" },
          title: { type: "string", description: "New title for the forum post." },
          archived: { type: "boolean", description: "Whether to archive the thread." },
          locked: { type: "boolean", description: "Whether to lock the thread." },
          applied_tags: {
            type: "array",
            items: { type: "string" },
            description: "Array of tag IDs to apply to the post.",
          },
        },
        required: ["thread_id"],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what fields can be updated. It lacks behavioral details such as required permissions, whether updates are reversible, rate limits, or error handling. This is a mutation tool, so transparency about side effects is crucial but missing.

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?

The description is a single, efficient sentence that front-loads the purpose and lists updatable fields without unnecessary words. Every part earns its place by directly informing the tool's function.

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 no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like permissions, side effects, or response format. Given the complexity of updating a forum post and the lack of structured data, more context is needed for safe and effective use.

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 description coverage is 80%, so the schema already documents most parameters well. The description adds minimal value by listing updatable fields (title, archived/locked status, applied tags), which aligns with schema properties but doesn't provide additional context like format examples or constraints beyond what's in the schema.

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 clearly states the action ('Update') and resource ('forum post') along with specific fields that can be modified (title, archived/locked status, applied tags). It distinguishes itself from siblings like 'discord_edit_message' or 'discord_delete_forum_post' by focusing on forum post updates, though it doesn't explicitly contrast with them.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention prerequisites like needing a thread_id or differentiate from similar tools like 'discord_edit_message' for non-forum contexts. The description only lists what can be updated, not when or why to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PaSympa/discord-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server