discp

modify_thread

Update a Discord thread by archiving, unarchiving, locking, unlocking, renaming, or setting slowmode to control conversation access and pacing.

Instructions

Update thread properties (archive/unarchive, lock/unlock, rename, slowmode)

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": {
      "threadId": "<threadId>"
    },
    "name": "modify_thread"
  }
}

Input Schema

Name	Required	Description
`name`	No	New thread name
`locked`	No	Lock thread (only moderators can speak)
`reason`	No	Audit log reason
`archived`	No	Archive (close) or unarchive thread
`slowmode`	No	Slowmode delay in seconds
`threadId`	Yes	Thread Channel ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 2, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral disclosure burden. It lists mutable properties but omits permission requirements, reversibility, audit-log implications, and whether the operations can be combined in a single call.

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 definition is a single front-loaded sentence with a compact parenthetical list of operations. There is no redundant or wasted text.

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 multi-property mutation tool with no annotations and no output schema, the description identifies the updateable fields but leaves prerequisites, side effects, and usage context undocumented. It is insufficiently complete for an agent to safely choose and invoke it without additional inference.

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 each parameter is already documented in the schema. The description maps its examples to name, archived, locked, and slowmode, but adds no syntax or constraint beyond what the schema provides, and it does not mention threadId or reason.

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 uses a specific verb and resource ('Update thread properties') and enumerates the mutable properties via parenthetical examples. It is clear what the tool does, but it does not explicitly differentiate itself from sibling tools such as edit_channel, modify_forum_post, or create_thread.

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?

The description states what can be updated but gives no when-to-use guidance, no prerequisites, and no exclusions. It never mentions alternatives like create_thread, join_thread, leave_thread, or edit_channel.

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

Deploy Server