Skip to main content
Glama
kuklaph
by kuklaph

Move or Rename Cascade Asset

cascade_move

Move an asset to a new container and/or rename it, with automatic reference updates.

Instructions

Move an asset to a new container and/or rename it.

Performs an in-place rename when newName is set but destinationContainerIdentifier is omitted, a pure move when destinationContainerIdentifier is set and newName is omitted, or both simultaneously when both are provided. References to the asset from other assets are updated automatically by Cascade.

Args:

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

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

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

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

  • moveParameters (object, required):

    • destinationContainerIdentifier (object, optional): Where to move the asset. Omit to keep in current container.

    • doWorkflow (boolean, required): Whether to run workflow on the move

    • newName (string, optional): New asset name. Omit to keep current name.

  • workflowConfiguration (object, optional, shape varies — see Cascade docs): Workflow step assignments

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

Examples:

  • Use when: "Rename /about/teem to /about/team" -> { identifier: { type: "page", id: "..." }, moveParameters: { doWorkflow: false, newName: "team" } }

  • Use when: "Move page to /archive" -> { identifier: { type: "page", id: "..." }, moveParameters: { doWorkflow: false, destinationContainerIdentifier: { type: "folder", path: { path: "/archive", siteName: "www" } } } }

  • Don't use when: You want to duplicate — use cascade_copy.

Error Handling:

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

  • "Destination not found" when destinationContainerIdentifier is invalid

  • "Name collision" when an asset with newName already exists in the destination

  • "Permission denied" when credentials lack move rights on source or destination. 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 move.
moveParametersNoMove parameters: destination container and/or new name.
workflowConfigurationNoOptional workflow configuration applied when doWorkflow=true.
Behavior4/5

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

Annotations indicate the tool is not read-only, not destructive, not idempotent, and open world. The description adds value by explaining automatic reference updates and providing detailed error handling messages. However, it does not discuss reversibility or side effects beyond reference updates, and the description includes some redundant system-level notes about responses that might not apply solely to this tool.

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?

The description is well-structured with sections (overview, args, returns, examples, error handling). It front-loads the core behavior. However, it is somewhat verbose, especially in the args section where it repeats schema details, and the system-level notes about structuredContent and oversized responses add noise but are likely required by the platform.

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?

Given the complexity of moving/renaming assets with optional workflow and reference updates, and no output schema, the description covers all essential information: return format, error handling, examples, and parameter interactions. It also refers to external documentation for complex subfields (workflowConfiguration), ensuring completeness for AI agent selection and invocation.

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%, and the description adds significant meaning beyond the schema. It explains the three operational modes (rename only, move only, both), details each parameter's subfields (e.g., identifier, moveParameters), and provides concrete examples showing how to structure calls for different use cases.

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 the tool moves or renames a Cascade asset, distinguishing it from sibling tools like cascade_copy (for duplication) and cascade_remove (for deletion). It uses a specific verb ('move or rename') and identifies the resource ('Cascade asset').

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?

The description explicitly states when to use (move/rename) and when not to use ('Don't use when: You want to duplicate — use cascade_copy'). Examples with 'Use when' and 'Don't use when' provide clear context. It also details three scenarios (rename only, move only, both) and specifies that references are updated automatically.

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