Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

acknowledge_pinned_messages

Mark a Discord channel's pinned messages as seen, clearing the pin acknowledgment state for that channel so unread pin indicators reset.

Instructions

Mark a channel's pins as seen. [POST /channels/{channel_id}/pins/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": "acknowledge_pinned_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
channel_idYesChannel ID (text, voice, thread, forum or DM channel)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/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 agent knows this is a non-destructive server-side write. The description adds the HTTP endpoint, which hints at the write path, but does not say what state changes (e.g., clearing an unread pin indicator) or whether the call is idempotent or requires permissions.

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?

Two short sentences, purpose first, endpoint second, with zero filler or redundant restatement of the tool name.

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

Completeness4/5

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

For a single-parameter mutation with no output schema and clear annotation coverage, the definition gives enough to invoke the tool correctly. Only side-effect details (what visibility state changes, permission requirements) are left implicit.

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?

Only one parameter exists and the schema documents it at 100% coverage, including which channel types are accepted. The description's phrase "a channel's pins" reinforces that channel_id scopes the acknowledgement, but adds no format or edge-case detail beyond the schema.

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 a channel's pins as seen") and the endpoint clarifies the target object, so an agent knows exactly what is affected. It does not explicitly distinguish itself from other acknowledge_* siblings, but the pin-specific resource is concrete enough to be identifiable.

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 guidance on when to call this versus alternatives, no preconditions (e.g., needing to be a channel member or having pins present), and no note on how often it should be invoked. The agent must infer usage entirely from the name.

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