events

Delete Event Preferences

delete_event_preferences

DestructiveIdempotent

Use this only when a user asks to delete their Dizko saved event preferences and feedback history.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`profile_id`	Yes
`confirm_delete`	Yes
`profile_secret`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedAug 30, 2026

removedInput schema / properties / confirm_delete / description

Removed value: -"Must be true only after the user confirms deletion of Dizko connector preferences and feedback history."

removedInput schema / properties / profile_id / description
```
Removed value: -"Stable user/profile id."
```

removedInput schema / properties / profile_secret / description

Removed value: -"Private profile secret returned when the profile was created."

changedOutput schema / (root)

Previous value: -{
-  "anyOf": [
-    {
-      "properties": {
-        "deleted": {
-          "type": "boolean"
-        }
-      },
-      "required": [
-        "deleted"
-      ],
-      "type": "object"
-    },
-    {
-      "properties": {
-        "assistant_instruction": {
-          "type": "string"
-        },
-        "cause": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "classification": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "code": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "error": {
-          "type": "string"
-        },
-        "hostname": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "retryable": {
-          "type": "boolean"
-        },
-        "status": {
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "type": {
-          "type": "string"
-        },
-        "url": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "required": [
-        "error"
-      ],
-      "type": "object"
-    }
-  ],
-  "type": "object"
-}New value: +null

Changed4 schema fields changedAug 24, 2026

addedInput schema / properties / confirm_delete / description

Added value: +"Must be true only after the user confirms deletion of Dizko connector preferences and feedback history."

addedInput schema / properties / profile_id / description
```
Added value: +"Stable user/profile id."
```

addedInput schema / properties / profile_secret / description

Added value: +"Private profile secret returned when the profile was created."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "anyOf": [
+    {
+      "properties": {
+        "deleted": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "deleted"
+      ],
+      "type": "object"
+    },
+    {
+      "properties": {
+        "assistant_instruction": {
+          "type": "string"
+        },
+        "cause": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "classification": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "code": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "error": {
+          "type": "string"
+        },
+        "hostname": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "retryable": {
+          "type": "boolean"
+        },
+        "status": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "type": {
+          "type": "string"
+        },
+        "url": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "error"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

Changed4 schema fields changedAug 24, 2026

removedInput schema / properties / confirm_delete / description

Removed value: -"Must be true only after the user confirms deletion of Dizko connector preferences and feedback history."

removedInput schema / properties / profile_id / description
```
Removed value: -"Stable user/profile id."
```

removedInput schema / properties / profile_secret / description

Removed value: -"Private profile secret returned when the profile was created."

changedOutput schema / (root)

Previous value: -{
-  "anyOf": [
-    {
-      "properties": {
-        "deleted": {
-          "type": "boolean"
-        }
-      },
-      "required": [
-        "deleted"
-      ],
-      "type": "object"
-    },
-    {
-      "properties": {
-        "assistant_instruction": {
-          "type": "string"
-        },
-        "cause": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "classification": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "code": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "error": {
-          "type": "string"
-        },
-        "hostname": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "retryable": {
-          "type": "boolean"
-        },
-        "status": {
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "type": {
-          "type": "string"
-        },
-        "url": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "required": [
-        "error"
-      ],
-      "type": "object"
-    }
-  ],
-  "type": "object"
-}New value: +null

First observedJul 30, 2026

TDQS

A4/5.0

Behavior4/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, and the description adds useful context about what gets destroyed: saved event preferences and feedback history. It also emphasizes that deletion should happen only when the user explicitly asks, which is a meaningful consent-oriented behavioral signal.

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?

The description is a single, front-loaded sentence with no filler. Every word contributes to clarifying the tool's purpose and usage condition, making it easy for an agent to scan and act on.

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?

The description is adequate for tool selection and clearly identifies the deletion scope, while annotations cover destructiveness and idempotency. However, it omits guidance on the confirmation flag, profile secret semantics, and what the result of deletion looks like, so invocation details are left mostly to schema names and inference.

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

Parameters2/5

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

Schema description coverage is 0%, and the description provides no parameter-specific information. The parameter names (profile_id, profile_secret, confirm_delete) are somewhat self-explanatory, but the description does not clarify how they should be used or that confirm_delete must be set to true to proceed.

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

Purpose5/5

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

The description states a specific verb (delete) and a specific resource (Dizko saved event preferences and feedback history), making the tool's purpose unambiguous. It also clearly distinguishes this from sibling tools like get_event_preferences, save_event_preferences, and create_event_preference_profile by focusing exclusively on deletion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives an explicit trigger: use this only when a user asks to delete their saved event preferences and feedback history. It does not name alternatives or provide when-not-to-use details, but the 'only when' phrasing provides clear routing context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All events tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?