Skip to main content
Glama
kuklaph
by kuklaph

Copy Cascade Asset

cascade_copy

Copy an asset to a different folder or site with a new name, creating an independent duplicate. The original asset remains unchanged.

Instructions

Copy an asset to a new container with a new name.

Creates a fresh, independent copy of an asset. Unlike cascade_move, the original stays in place and the copy gets its own ID. destinationContainerIdentifier and newName are both required. For copying an entire site, use cascade_site_copy instead.

Args:

  • identifier (object, required): The source asset to copy

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

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

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

  • copyParameters (object, required):

    • destinationContainerIdentifier (object, required): The container (folder/site) that will receive the copy

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

    • newName (string, required): Name for the new asset (must be unique within destination)

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

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

Examples:

  • Use when: "Duplicate /templates/basic as /templates/basic-v2" -> { identifier: { type: "page", path: { path: "/templates/basic", siteName: "www" } }, copyParameters: { destinationContainerIdentifier: { type: "folder", path: { path: "/templates", siteName: "www" } }, newName: "basic-v2", doWorkflow: false } }

  • Don't use when: You want to rename in place — use cascade_move.

  • Don't use when: You want to copy an entire site — use cascade_site_copy.

Error Handling:

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

  • "Destination not found" when destinationContainerIdentifier is invalid

  • "Name collision" when newName already exists in destination

  • "Permission denied" when credentials lack read on source or create on 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 copy.
copyParametersNoCopy parameters: destination, new name, and workflow flag.
workflowConfigurationNoOptional workflow configuration applied when doWorkflow=true.
Behavior4/5

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

Annotations already indicate non-read-only and non-destructive; description adds that the original stays and copy gets its own ID, destination and name are required, and workflow can be run. However, there is a trailing paragraph about response formats and cascade_read that seems irrelevant and slightly confusing.

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 structured with clear sections (Args, Returns, Examples, Error Handling). However, the error handling section includes unrelated text about JSON responses and cascade_read, and there is minor repetition ('both required'). Still mostly concise.

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 tool with 3 complex parameters and no output schema, the description covers purpose, parameter details, examples, error handling, and usage guidelines. It provides a complete picture despite the minor irrelevant text.

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?

The input schema has minimal descriptions (100% coverage but vague). The description elaborates on each parameter, including nested structure, required fields within copyParameters, and examples. This adds significant meaning 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 the tool copies an asset to a new container with a new name, creating an independent copy. It distinguishes itself from siblings like cascade_move (original stays) and cascade_site_copy (for sites).

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 (duplicate an asset) and when-not-to-use (rename in place → cascade_move, copy site → cascade_site_copy). Includes an example and error handling scenarios.

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