Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

delete_notification_settings_snapshot

Destructive

Deletes a Discord notification settings snapshot by snapshot ID, letting you remove outdated or unwanted saved notification preferences.

Instructions

Delete Notification Settings Snapshot. [DELETE /users/@me/notification-settings/snapshots/{snapshot_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": {
      "snapshot_id": "<snapshot_id>"
    },
    "name": "delete_notification_settings_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
snapshot_idYesSnapshot ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/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 safety profile is known; the description adds nothing on top. It does not say whether deletion is permanent or whether the snapshot can be recreated, nor does it mention any auth or ownership requirement for the snapshots/{snapshot_id} path, which matters for a destructive call.

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 fragments with no filler; the action and target arrive first and the HTTP endpoint follows as supporting detail. Slightly wasteful in that the endpoint restates what the name already implies, but nothing is buried.

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 destructive, irreversible-sounding mutation with no output schema and an opaque domain concept ("snapshot"). The description leaves the agent without the meaning of the resource, recoverability, or the workflow context needed to call it responsibly, which is inadequate for a delete 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?

Only one parameter exists and schema description coverage is 100%, so the schema already carries snapshot_id. The endpoint template corroborates where the ID goes in the path, but the description adds no format, provenance, or lookup hints (e.g., obtainable from list_notification_settings_snapshots), landing at the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ("Delete Notification Settings Snapshot") and the endpoint path confirms the target is a snapshot scoped to the current user. However, it never explains what a notification-settings snapshot is, and it does nothing to separate this from the sibling create_/list_notification_settings_snapshots tools beyond the verb.

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 a snapshot versus restoring/using it, nor any pointer to the create_ or list_ siblings that naturally precede this call. An agent must infer the workflow entirely.

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