Skip to main content
Glama

Close or reopen post

discord_set_post_status
Idempotent

Close or reopen a Discord forum post, optionally posting a note before closing. Closing archives the post without deleting it and can be reversed.

Instructions

Close (archive) or reopen a forum post. Closing is reversible and does not delete anything. Optionally post a closing note first.

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_id": "<post_id>",
      "closed": "<closed>"
    },
    "name": "discord_set_post_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoMessage to post before closing
closedYestrue to close, false to reopen
post_idYesForum post ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description reinforces the non-destructive profile ("reversible and does not delete anything") and adds the note-before-close behavior, which is useful but largely restates what the annotations imply. It says nothing about required permissions for closing posts, which would have added real value for an openWorld 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?

Two short sentences with zero filler, front-loading the action before the safety reassurance and the optional note. Every clause conveys information an agent can act on.

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 simple three-parameter toggle tool with full schema coverage and annotations covering the safety profile, this is nearly complete. The only minor gap is whether a note can also be attached when reopening, or what the response looks like on success.

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 100%, so post_id, closed, and note are fully documented in the schema. The description only restates the note purpose ("post a closing note first") and adds no format, length, or edge-case detail beyond the schema. Baseline 3 is correct when the schema carries the parameter burden.

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 opens with a specific verb pair and resource: "Close (archive) or reopen a forum post." That is unambiguous and clearly distinct from siblings like discord_set_post_tags or discord_create_post. It doesn't explicitly name or contrast a sibling, which keeps it from a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear context for both modes via the closed flag (close vs reopen) and mentions the optional note-first workflow. There are no exclusions or named alternatives, so an agent gets adequate but not exhaustive when-to-use guidance.

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