Skip to main content
Glama
kuklaph
by kuklaph

Delete Message

cascade_delete_message
DestructiveIdempotent

Permanently remove a message from your mailbox. This action is irreversible; archive messages for retention.

Instructions

Permanently delete a message from the authenticated user's Cascade mailbox.

This is a DESTRUCTIVE operation — once deleted, the message cannot be recovered (archive is not the same as recycle-bin for messages). Prefer cascade_mark_message with markType: "archive" for retention. Messages must belong to the authenticated user; you cannot delete messages in another user's mailbox.

Args:

  • identifier (object, required): The message to delete

    • id (string, required): Message ID (from cascade_list_messages)

    • type (string, required): Must be "message"

Returns: Cascade OperationResult: { success: true } On failure: { success: false, message: "" }

Examples:

  • Use when: "Permanently clear spam-like notifications" -> { identifier: { type: "message", id: "..." } }

  • Don't use when: You want to hide it without deleting — use cascade_mark_message with markType: "archive".

  • Don't use when: You want to delete in bulk — this deletes one message per call.

Error Handling:

  • "Message not found" when the identifier doesn't resolve

  • "Permission denied" when the message belongs to another user. Responses are JSON text; structuredContent is authoritative when the response fits. Oversized responses return bounded _cache metadata for cascade_read_response. For cascade_read, read_mode controls preview versus raw Cascade payload shape.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identifierNoThe message to delete.
Behavior5/5

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

Annotations already mark destructiveHint and idempotentHint. The description adds crucial details: operation is irreversible, no recovery, permission checks, and error handling messages. No contradiction with annotations.

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?

Well-structured with clear sections (Args, Returns, Examples, Error Handling). However, the final paragraph about cascade_read and responses is unrelated to this tool and adds noise, slightly reducing conciseness.

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

Completeness5/5

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

For a simple tool with one parameter and no output schema, the description covers purpose, parameters, usage, errors, and expected behavior completely.

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

Parameters5/5

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

Despite 100% schema coverage, the description explains the identifier parameter structure, required fields (id, type), and that id comes from cascade_list_messages. Adds meaningful context beyond the schema.

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 clearly states it permanently deletes a message from the authenticated user's Cascade mailbox. It distinguishes from siblings like cascade_mark_message (archive) and indicates it's not for bulk deletion.

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

Usage Guidelines5/5

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

Provides explicit when-to-use (permanently clear spam) and when-not-to-use (use archive instead, no bulk deletion). Also specifies that messages must belong to the authenticated user.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kuklaph/cascade-cms-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server