Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

bulk_update_read_states

Marks multiple Discord channels as read in one request using channel and message IDs, reducing repetitive manual acknowledgements.

Instructions

Mark many channels read: read_states [{channel_id, message_id}]. [POST /read-states/ack-bulk]

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": {
      "read_states": "<read_states>"
    },
    "name": "bulk_update_read_states"
  }
}

Input Schema

NameRequiredDescriptionDefault
read_statesYesread states

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 readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered; the description adds only the HTTP endpoint path. For a bulk mutation it says nothing about array size limits, per-item failure behavior, partial success, or idempotency — the details an agent most needs before sending many IDs at once.

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?

One front-loaded sentence plus an endpoint tag — no filler. Every element carries information, though the minimalism is also the source of the semantic gaps scored elsewhere.

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?

With one parameter, no nested objects and no output schema, the description covers the basic call shape adequately. It is incomplete for a bulk mutation: batch-size limits, partial-failure semantics, and the effect on unread counts are all unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is nominally 100%, but the schema's only description is the uninformative "read states" and the item schema is an empty object. The description supplies the actual item shape [{channel_id, message_id}], which is genuine meaning beyond the schema; it does not say whether message_id is optional or what sets a channel fully read.

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 specific verb and resource ("Mark many channels read") plus the bulk payload, so the operation is identifiable. However, it gives no differentiation from siblings such as mark_read or delete_read_state, leaving the agent to infer that this is the plural/batch form.

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 statement of when to prefer this over mark_read (one channel) or delete_read_state (un-read), and no prerequisites or exclusions. The plural "many channels" implies bulk usage, but the agent must infer the selection rule from the name 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