Clypmint

Remove a layer

delete_layer

DestructiveIdempotent

Removes an ov_ or vo_ layer, or hides a layer; cut takes time out. Cost: Free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "layer_id": "<layer_id>"
    },
    "name": "delete_layer"
  }
}

Input Schema

Name	Required	Description
`layer_id`	Yes	An ov_ or vo_ layer (removed), or a get_timeline layer (hidden; update_layer hidden false shows it).
`video_id`	No	Video; the open one if left out.
`output_id`	No	Output id.
`base_version`	No	Version id you read.
`operation_id`	No	Same id retries run once.
`selected_layer_id`	No	Selected layer id.

Output Schema

Name	Required	Description	Default
`code`	No
`cost`	No
`error`	No
`state`	No
`status`	No
`dry_run`	No
`message`	No
`plan_id`	No
`style_id`	No
`video_id`	No
`available`	No
`import_id`	No
`output_id`	No
`studio_url`	No
`version_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 7, 2026

changedInput schema / properties / layer_id / description

Previous value: -"An ov_ overlay (removed) or a layer from get_timeline (hidden; update_layer hidden false shows it again)."New value: +"An ov_ or vo_ layer (removed), or a get_timeline layer (hidden; update_layer hidden false shows it)."

changedInput schema / properties / video_id / description

Previous value: -"The video; the open one when left out."New value: +"Video; the open one if left out."

Changed6 schema fields changedNov 6, 2026

changedInput schema / properties / base_version / description

Previous value: -"The version_id you read; refused if the video changed since."New value: +"Version id you read."

changedInput schema / properties / operation_id / description

Previous value: -"A retry with the same id runs once."New value: +"Same id retries run once."

changedInput schema / properties / output_id / description

Previous value: -"An output (Short, hook, shape); the main video when left out."New value: +"Output id."

addedInput schema / properties / selected_layer_id

Added value: +{
+  "description": "Selected layer id.",
+  "maxLength": 160,
+  "minLength": 1,
+  "type": "string"
+}

changedInput schema / properties / video_id / description

Previous value: -"The video, from list_videos."New value: +"The video; the open one when left out."

changedInput schema / required

Previous value: -[
-  "video_id",
-  "layer_id"
-]New value: +[
+  "layer_id"
+]

Changed3 schema fields changedNov 1, 2026

changedInput schema / properties / base_version / description

Previous value: -"The version_id you read; refused if the video changed since. Left out: the live version, and a repeat is saved once."New value: +"The version_id you read; refused if the video changed since."

changedInput schema / properties / operation_id / description

Previous value: -"The same id on a retry runs it once; a new id is a new request."New value: +"A retry with the same id runs once."

changedInput schema / properties / output_id / description

Previous value: -"A Short, hook or shape of the video; the main video when left out."New value: +"An output (Short, hook, shape); the main video when left out."

AddedOct 31, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that — deletion vs. hiding depends on layer type, and the operation is free — but it omits reversibility, permission requirements, and the meaning of 'cut takes time out'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is short and front-loads the verb, which is good, but 'cut takes time out' is an unparsable fragment that occupies space without conveying actionable meaning. The 'Cost: Free' note earns its place; the middle clause does not.

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?

With an output schema, full parameter documentation, and rich annotations, the description only needs to cover the dual-mode behavior and cost, which it does. It leaves an agent guessing about the effect on the cut, whether deletion is recoverable, and how hiding interacts with downstream state — meaningful gaps for a destructive tool.

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

Parameters3/5

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

Schema description coverage is 100%, so all six parameters including layer_id semantics and retry behavior via operation_id are already documented in the schema. The description's layer-type distinction duplicates what the layer_id description already states, so baseline 3 applies.

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

Purpose4/5

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

States a specific verb+resource ('Removes an ov_ or vo_ layer') and adds the second mode ('or hides a layer'), which tells an agent the tool has two distinct outcomes. It does not name the sibling that performs the inverse (update_layer) or otherwise differentiate from it, so it falls short of a 5.

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

Usage Guidelines3/5

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

The layer-type prefix (ov_/vo_ vs. get_timeline layers) implicitly tells the agent which mode will be applied, which is a usable routing signal. However, there is no explicit when-to-use/when-not guidance, no mention of update_layer as the way to unhide, and the phrase 'cut takes time out' is too cryptic to serve as a usage caveat.

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

All Clypmint 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?