Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

acknowledge_message

Mark a Discord channel as read up to a specific message, clearing unread status from that point onward.

Instructions

Mark a channel as read up to a message. (mark_read does this for you.) [POST /channels/{channel_id}/messages/{message_id}/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>",
      "message_id": "<message_id>"
    },
    "name": "acknowledge_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNo
manualNomanual
channel_idYesChannel ID (text, voice, thread, forum or DM channel)
message_idYesMessage ID
last_viewedNolast viewed
mention_countNomention count

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare destructiveHint=false and openWorldHint=true, so the safety profile is covered. Beyond that the description only restates the HTTP endpoint; it does not explain what the mutation actually records, whether it is idempotent, or what the undocumented fields (manual, last_viewed, mention_count) change about the ack state.

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?

Front-loaded with the action and scope in the first clause, followed by a short routing hint and the endpoint. No padding; the only weakness is that the endpoint notation is administrative detail rather than agent-relevant guidance.

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?

This is a mutating tool with six parameters, four of them poorly explained and no output schema. The description does not say what the call returns, what happens to the channel's read state, or how the optional overrides interact, which is insufficient for a write operation of this shape.

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 83%, so the baseline is 3. The description adds nothing about parameter meaning, and several schema descriptions are tautological (e.g. 'manual', 'last viewed'), so the ambiguity around overriding read position is not resolved by either source.

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?

States a concrete verb and resource: marking a channel read up to a specific message, and the bracketed route confirms it targets a single message in a channel. It also gestures at the distinction from the sibling mark_read, though it leaves it ambiguous whether this is a lower-level variant of that tool or a redundant one.

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 parenthetical '(mark_read does this for you.)' implies agents should usually prefer mark_read and reach for this tool only in special cases. However, it never states what those special cases are, so the when-to-use-this-instead condition is left to inference.

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