Clypmint

Cut time out

cut

DestructiveIdempotent

Take time out by seconds or word numbers; the gap closes. Cost: Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cut"
  }
}

Input Schema

Name	Required	Description
`words`	No	[first, last] word numbers from get_transcript to take out.
`ranges`	No	Film seconds to take out, [[from, to], ...], on the version read.
`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.

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.

Changed1 schema field changedNov 10, 2026
- removedInput schema / properties / operation_id / pattern
```
Removed value: -"^[a-zA-Z0-9_.:-]{1,100}$"
```

Changed2 schema fields changedNov 7, 2026

changedInput schema / properties / ranges / description

Previous value: -"Film seconds to take out, [[from, to], ...] on the version you read."New value: +"Film seconds to take out, [[from, to], ...], on the version read."

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."

Changed5 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."

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"
-]New value: +[]

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."

Changed6 schema fields changedOct 31, 2026

changedInput schema / properties / ranges / items / items

Previous value: -[
-  {
-    "maximum": 36000,
-    "minimum": 0,
-    "type": "number"
-  },
-  {
-    "maximum": 36000,
-    "minimum": 0,
-    "type": "number"
-  }
-]New value: +{
+  "maximum": 36000,
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / ranges / items / maxItems
```
Added value: +2
```
addedInput schema / properties / ranges / items / minItems
```
Added value: +2
```

changedInput schema / properties / words / items

Previous value: -[
-  {
-    "maximum": 9007199254740991,
-    "minimum": 0,
-    "type": "integer"
-  },
-  {
-    "maximum": 9007199254740991,
-    "minimum": 0,
-    "type": "integer"
-  }
-]New value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / words / maxItems
```
Added value: +2
```
addedInput schema / properties / words / minItems
```
Added value: +2
```

AddedOct 31, 2026

TDQS

B3.2/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 one genuinely useful behavioral fact beyond them: "the gap closes," telling the agent that subsequent content ripples to fill the removed segment. It still omits reversibility/undo and what happens if both words and ranges are supplied, so it is not rich.

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?

Two short clauses, front-loaded with the action and the key consequence; nothing is padded. The appended "Cost: Free" is commercial boilerplate that does not help an agent invoke the tool correctly, keeping it from a 5.

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 present and full schema descriptions plus destructive/idempotent annotations, most of the burden is already carried. Still, for a destructive timeline mutation the description leaves unaddressed whether the cut is reversible and how the two input modes interact — gaps an agent would want before calling it.

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 are already documented, establishing the baseline of 3. The phrase "by seconds or word numbers" does add the useful hint that `ranges` and `words` are alternative ways of specifying the cut, but it does not state whether they are mutually exclusive or how they combine when both are passed.

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?

"Take time out by seconds or word numbers; the gap closes" states a specific verb (remove a segment) on a specific resource (a video's timeline), and names the two input modes. It is clear but never names a sibling or explicitly frames itself as the ripple-delete counterpart to edit_video/delete_layer, so an agent must infer the distinction.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no alternatives are mentioned. The only extra information is the pricing note "Cost: Free," which does not help an agent decide between this and trimming via edit_video or removing a whole layer.

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?