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 thread

update_thread

Rename, archive or unarchive, lock or unlock a Discord thread, and change its slowmode or auto-archive window to control thread settings.

Instructions

Rename a thread, archive or unarchive it, lock or unlock it, or change its slowmode and auto-archive window.

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": {
      "thread": "<thread>"
    },
    "name": "update_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
guildNoGuild (server) name or ID. Omit to use the default guild.
lockedNo
threadYesThread name or ID.
archivedNo
slowmode_secondsNo
auto_archive_minutesNo

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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered. The description usefully clarifies that this is a partial/field-level mutation of an existing thread rather than a replace. However, it does not disclose permission requirements or side effects such as archiving making a thread read-only, which matters 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence, front-loaded with the primary action and enumerating the rest compactly. No filler or restatement of the title. The only weakness is that the operation list is comma-chained rather than structured, but it stays readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a seven-parameter mutation tool with no output schema and sparse schema descriptions, the definition covers the main operations but omits permission prerequisites, whether unspecified fields are left untouched, and what happens on archive. Adequate to invoke, but not fully sufficient to call correctly in edge cases.

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 coverage is only 29% (only guild and thread carry descriptions), so the description has to compensate. It does add meaning by mapping plain-language operations to the fields name, archived, locked, slowmode_seconds, and auto_archive_minutes, which is most of the seven parameters. It adds nothing for guild/thread semantics or for valid slowmode/auto-archive ranges beyond the enum the schema already lists.

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+resource ('Rename a thread') and enumerates the exact mutations supported: archive/unarchive, lock/unlock, slowmode, auto-archive. This clearly separates it from create_thread, delete_thread, and get_thread. It stops short of naming siblings, but the operation list is unambiguous.

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?

There is no explicit when-to-use guidance, no mention of required permissions (manage_threads or similar), and no statement about which sibling to pick for reading versus creating versus deleting. The agent must infer that this is the mutation tool from the verb list alone.

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