Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

delete_notification_center_item

Destructive

Deletes a specified item from Discord's Notification Center using its item ID to clear unwanted account notifications.

Instructions

Delete Notification Center Item. [DELETE /users/@me/notification-center/items/{item_id}]

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": {
      "item_id": "<item_id>"
    },
    "name": "delete_notification_center_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYesNotification item ID
item_typeNoitem type

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the description only needs to add context. It adds none: nothing about whether the deletion is permanent or reversible, whether it affects only the calling user, or what happens on an invalid item_id.

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 no filler; the endpoint reference is compact and useful. The terseness borders on under-specification, but nothing is wasted.

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 low-complexity, single-target destructive call with full annotation and schema coverage, the essentials are present. Missing are the delete-vs-acknowledge decision and any note about irreversibility, which matter for a destructive operation.

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% for both parameters (item_id, item_type), so the schema already carries the semantics and a baseline 3 applies. The description contributes no additional meaning about how item_type interacts with item_id or whether it is required.

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 specific verb and resource ("Delete Notification Center Item") and pins it to a concrete endpoint, so an agent can tell it removes a single notification item rather than acknowledging or listing one. It stops short of naming the sibling that performs the non-destructive counterpart.

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 delete versus when to use acknowledge_notification_center_item or bulk_acknowledge_notification_center_items. The agent must infer the alternative from sibling names 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