Clypmint

Add a clip with its sound

add_clip

Idempotent

Puts another of their videos in, with its own sound. 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": {
      "asset_id": "<asset_id>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "add_clip"
  }
}

Input Schema

Name	Required	Description
`at`	No	Film second it goes in (the rest moves later); the end if left out.
`to`	Yes	The clip's last second to play.
`from`	Yes	The clip's first second to play.
`asset_id`	Yes	A video asset_id from import_media or list_assets.
`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.

Changed2 schema fields changedNov 10, 2026
- removedInput schema / properties / asset_id / pattern
```
Removed value: -"^src_[A-Za-z0-9_-]{8,96}$"
```
- removedInput schema / properties / operation_id / pattern
```
Removed value: -"^[a-zA-Z0-9_.:-]{1,100}$"
```

Changed2 schema fields changedNov 7, 2026

changedInput schema / properties / at / description

Previous value: -"The film second it goes in (everything after moves later); the end when left out."New value: +"Film second it goes in (the rest moves later); the end if left out."

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",
-  "asset_id",
-  "from",
-  "to"
-]New value: +[
+  "asset_id",
+  "from",
+  "to"
+]

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

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds that the clip carries its own sound (audio is included, not stripped) and that the operation is free/billed, which is genuine context beyond annotations, but it does not disclose the non-destructive ripple behavior the schema hints at ('the rest moves later').

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 sentences with the action front-loaded and no filler. The phrasing 'Puts another of their videos in' is conversational and slightly ambiguous, and 'Cost: Free' is marginal, but the definition is efficiently sized.

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?

For an 8-parameter timeline mutation with an output schema available, the description is thin: it omits how insertion interacts with existing clips, version/operation_id concurrency expectations, and what the returned output represents. The rich schema prevents this from being inadequate, but the description does not carry its share for a mutating 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 every parameter including at/from/to semantics, asset_id sourcing, and operation_id retry semantics is already documented. The description adds nothing parameter-specific, so the baseline 3 applies.

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

Purpose3/5

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

The description conveys the core action (insert a video segment together with its own audio), but 'Puts another of their videos in' is vague about the target (timeline/output) and never distinguishes this from related siblings such as add_voiceover or save_clip. It is understandable but not precise.

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?

There is no statement of when to use this versus alternatives, no prerequisites (e.g. needing an asset_id from import_media, or a base_version for concurrency), and no exclusions. The only guidance-like content is the pricing note 'Cost: Free.'

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?