Skip to main content
Glama
kuklaph
by kuklaph

Remove (Delete) Cascade Asset

cascade_remove
DestructiveIdempotent

Delete assets from Cascade CMS, sending to recycle bin by default. Optionally unpublish or hard-delete. Confirm intent before use.

Instructions

Delete an asset from Cascade CMS.

By default, deletion sends the asset to the recycle bin; deleteParameters can unpublish and/or hard-delete. Site removal and root-folder path "/" removal are rejected; root-folder ID safeguards require generated tool-block rules. If the asset is under a workflow that requires review, workflowConfiguration specifies the approval flow. This is a DESTRUCTIVE operation — confirm intent before calling.

Args:

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

    • id (string, optional): Asset ID (preferred)

    • path (object, optional): { path, siteId OR siteName }

    • type (string, required): Entity type of the asset

  • deleteParameters (object, optional, shape varies — see Cascade docs): Controls delete behavior

    • doWorkflow (boolean): Whether to run the workflow on delete

    • unpublish (boolean): Unpublish from destinations before deleting

  • workflowConfiguration (object, optional, shape varies — see Cascade docs): Workflow step assignments when user can't bypass workflow

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

Examples:

  • Use when: "Delete a page" -> { identifier: { type: "page", id: "..." } }

  • Use when: "Unpublish then delete" -> { identifier: { type: "page", id: "..." }, deleteParameters: { unpublish: true } }

  • Don't use when: You just want to move/rename — use cascade_move.

  • Don't use when: You want to unpublish without deleting — use cascade_publish_unpublish with unpublish: true.

Error Handling:

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

  • "Permission denied" when credentials lack delete rights

  • "Asset has children" when deleting a non-empty folder without cascade

  • "Workflow required" when the container requires workflow and none was supplied. 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 asset to remove (moves to recycle bin by default).
workflowConfigurationNoOptional workflow configuration to apply during removal. Matches Cascade's WorkflowConfiguration shape.
deleteParametersNoOptional delete parameters (e.g., to bypass the recycle bin or unpublish first). Matches Cascade's DeleteParameters shape.
Behavior4/5

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

Annotations already indicate destructiveHint=true; description adds value by detailing default recycle-bin behavior, hard-delete/unpublish options, rejected operations (site removal), workflow requirements, and a warning label. 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 Args, Returns, Examples, and Error Handling sections. Front-loaded with key purpose. Slightly lengthy due to examples and error details, but remains efficient and organized for a complex tool.

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?

Covers all inputs with examples and error handling, explains return format, and references relevant sibling behavior (cascade_read_response). Despite no output schema, description provides complete guidance for safe usage.

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?

Schema coverage is 100% with param descriptions; description further enriches by explaining default behavior (recycle bin), specifying shape of identifier, detailing deleteParameters (doWorkflow, unpublish), and workflowConfiguration with examples. Adds significant meaning beyond 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 'Delete an asset from Cascade CMS' with specific verb and resource, and explicitly distinguishes from siblings like cascade_move and cascade_publish_unpublish in the 'Don't use when' examples.

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 scenarios (delete, unpublish then delete) and when-not-to-use with alternatives (cascade_move, cascade_publish_unpublish). Also includes error handling for common failure modes, guiding correct invocation.

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