Clypmint

Make an editing style

copy_style

DestructiveIdempotent

Build a reusable editing style from one reference video shared by link or file. mode clone (the default) is the deep copy: it measures the reference and writes its own captions and motion; the linked account includes style copies every month at no credit cost, and once they are used each costs 100 credits. mode match is the fast copy: it maps the reference onto Clypmint's own devices in a few minutes, is included for every account and is approximate. A copy that is still working or has stopped shows in browse_styles (with its time left, or why it stopped and how to try again). dry_run: true answers whether this one is included (and how many are left) or what it costs, and starts nothing.

Input Schema

Name	Required	Description
`mode`	No	clone (default): deep, copies the reference's own motion and captions; slower; uses a monthly style copy, then credits. match: fast and approximate; included for every account.
`name`	No
`format`	No
`dry_run`	No	true: answer the cost and start nothing.
`reference`	No
`operation_id`	No	A stable ID for this authorized request. Preserve it on retries. Use a new ID only for a deliberate new request.
`reference_url`	No

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 changedOct 20, 2026

addedInput schema / properties / mode

Added value: +{
+  "description": "clone (default): deep, copies the reference's own motion and captions; slower; uses a monthly style copy, then credits. match: fast and approximate; included for every account.",
+  "enum": [
+    "clone",
+    "match"
+  ],
+  "type": "string"
+}

Changed1 schema field changedOct 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Clypmint copy_style result. Error results carry error; successful requests expose the identifiers and state available for the next step. Signed media stays in private metadata.",
+  "properties": {
+    "available": {
+      "type": "boolean"
+    },
+    "code": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "cost": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "dry_run": {
+      "type": "boolean"
+    },
+    "error": {
+      "type": "string"
+    },
+    "import_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "message": {
+      "type": "string"
+    },
+    "output_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "plan_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "state": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "type": [
+        "string",
+        "integer",
+        "null"
+      ]
+    },
+    "studio_url": {
+      "format": "uri",
+      "type": "string"
+    },
+    "style_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "version_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "video_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedOct 12, 2026

addedInput schema / properties / dry_run

Added value: +{
+  "description": "true: answer the cost and start nothing.",
+  "type": "boolean"
+}

Changed1 schema field changedOct 10, 2026
- addedInput schema / properties / format / type
```
Added value: +"string"
```

Changed1 schema field changedOct 6, 2026

addedInput schema / properties / format

Added value: +{
+  "enum": [
+    "talking",
+    "faceless",
+    "motion"
+  ]
+}

Changed1 schema field changedOct 6, 2026

addedInput schema / properties / operation_id

Added value: +{
+  "description": "A stable ID for this authorized request. Preserve it on retries. Use a new ID only for a deliberate new request.",
+  "pattern": "^[a-zA-Z0-9_.:-]{1,100}$",
+  "type": "string"
+}

First observedOct 3, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, yet the description still adds meaningful behavior: credit economics (monthly included copies, then 100 credits each), rough timing for match (a few minutes), the approximate-vs-deep fidelity difference, and that in-progress/failed copies surface in browse_styles with remaining time or a stop reason. It does not explain what the destructiveHint implies (e.g., whether an existing style is overwritten), which is the one notable gap.

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 lead sentence front-loads purpose, and the mode/cost/dry_run sentences each carry distinct information. It is somewhat dense with colon-chained clauses, and the mode economics partially repeat the enum description in the schema, but there is little outright filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need no explanation, and the description covers the operationally critical facts: mode selection, cost and inclusion rules, dry-run behavior, and where to check status. It is slightly incomplete on the undocumented name/format parameters and on the destructive semantics flagged by annotations.

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 only 43%, and the description compensates well for mode (elaborating depth, cost, and inclusion beyond the enum doc) and dry_run, plus confirming reference can come as link or file. It says nothing about name, format (talking/faceless/motion), or reference_url, so several parameters remain undocumented across both the schema and the description.

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?

"Build a reusable editing style from one reference video shared by link or file" gives a specific verb (build), a specific resource (reusable editing style), and the required input source (reference video via link or file). It also differentiates from the sibling browse_styles by positioning that tool as where in-progress/failed copies are tracked.

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

Usage Guidelines4/5

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

The clone-vs-match tradeoff is spelled out with concrete conditions: clone is the deep default that consumes a monthly style copy then 100 credits each, match is fast, approximate, and included for all accounts, and dry_run answers cost/eligibility without starting anything. What's missing is routing guidance against siblings like adjust_style or apply_edits, so the agent knows when this tool is the right entry point versus modifying an existing style.

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?