Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

delete_read_state

Destructive

Marks a Discord channel as unread by deleting its read state, resetting acknowledgment so the channel appears with unread messages.

Instructions

Mark a channel as unread (delete its read state). [DELETE /channels/{channel_id}/messages/ack]

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": {
      "channel_id": "<channel_id>"
    },
    "name": "delete_read_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNoversion
channel_idYesChannel ID (text, voice, thread, forum or DM channel)
read_state_typeNoread state type

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation/risk profile is covered. The description adds the key clarifying fact that the deleted read state means the channel becomes unread, but it omits important behavioral detail: whether this clears the read marker for the calling user only or for everyone, and whether the previous ack position can be restored. The bracketed endpoint is developer-facing metadata rather than behavioral context.

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?

Two short, front-loaded sentences with the primary effect first and the rename disambiguation immediately after. The HTTP endpoint in brackets is arguably extra, but it is compact and useful for API mapping.

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 small single-target mutation with a fully documented schema and annotations, most of what's needed is present; the critical missing piece is scope — whether the read state being deleted is per-user or shared — which materially affects whether an agent should call this at all.

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 channel_id, version and read_state_type are already documented in the schema. The description contributes nothing to parameter meaning — notably it never explains what 'version' is for or when read_state_type must be set — so the baseline 3 applies.

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 states a concrete verb and resource ('Mark a channel as unread') and bridges the gap between the tool's name (delete_read_state) and its user-visible effect, so an agent isn't misled by the 'delete' wording. It does not explicitly contrast with mark_read or bulk_update_read_states, so sibling differentiation is left implicit.

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?

The use case is implied by naming the outcome (mark a channel unread), which is enough to infer when to call it, but there is no explicit when-not guidance and the bulk variant sibling is never mentioned despite being a plausible alternative for multi-channel cases.

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