Clypmint

Change the sound

set_audio

DestructiveIdempotent

Music, exact sound effects, the style's own effects, and the footage sound. 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": "set_audio"
  }
}

Input Schema

Name	Required	Description
`music`	No	The music.
`video_id`	No	Video; the open one if left out.
`output_id`	No	Output id.
`base_version`	No	Version id you read.
`camera_sound`	No	The footage's own sound.
`house_sounds`	No	The style's own sound effects.
`operation_id`	No	Same id retries run once.
`sound_effects`	No	Exact sound effects, all in one save.

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.

Changed4 schema fields changedNov 10, 2026
- removedInput schema / properties / music / properties / asset_id / pattern
```
Removed value: -"^src_[A-Za-z0-9_-]{8,96}$"
```
- removedInput schema / properties / music / properties / music_staging_key / pattern
```
Removed value: -"^stg_[A-Za-z0-9][A-Za-z0-9_-]{7,95}$"
```
- removedInput schema / properties / operation_id / pattern
```
Removed value: -"^[a-zA-Z0-9_.:-]{1,100}$"
```
- removedInput schema / properties / sound_effects / items / properties / sound_id / pattern
```
Removed value: -"^sfx_[a-f0-9]{16}$"
```

Changed1 schema field changedNov 7, 2026

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

Changed6 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 / music / properties / music_staging_key / description

Previous value: -"Or a song attached in the chat: the music_staging_key import_asset gave."New value: +"Or a song attached in the chat (from import_asset)."

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

removedInput schema / properties / sound_effect

Removed value: -{
-  "additionalProperties": false,
-  "description": "One exact sound effect.",
-  "properties": {
-    "align": {
-      "description": "Which part of it lands on at: onset (default), peak or end.",
-      "enum": [
-        "onset",
-        "peak",
-        "end"
-      ],
-      "type": "string"
-    },
-    "at": {
-      "description": "The film second it lands.",
-      "maximum": 7200,
-      "minimum": 0,
-      "type": "number"
-    },
-    "gain_db": {
-      "description": "dB under the voice; -20 when left out.",
-      "maximum": -10,
-      "minimum": -36,
-      "type": "number"
-    },
-    "remove": {
-      "const": true,
-      "description": "true takes this sound out (the one nearest at, or every placement).",
-      "type": "boolean"
-    },
-    "sound_id": {
-      "description": "A sound_id from search_sounds.",
-      "pattern": "^sfx_[a-f0-9]{16}$",
-      "type": "string"
-    }
-  },
-  "required": [
-    "sound_id"
-  ],
-  "type": "object"
-}

addedInput schema / properties / sound_effects

Added value: +{
+  "description": "Exact sound effects, all in one save.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "align": {
+        "description": "Which part of it lands on at: onset (default), peak or end.",
+        "enum": [
+          "onset",
+          "peak",
+          "end"
+        ],
+        "type": "string"
+      },
+      "at": {
+        "description": "The film second it lands.",
+        "maximum": 7200,
+        "minimum": 0,
+        "type": "number"
+      },
+      "gain_db": {
+        "description": "dB under the voice; -20 when left out.",
+        "maximum": -10,
+        "minimum": -36,
+        "type": "number"
+      },
+      "remove": {
+        "const": true,
+        "description": "true takes this sound out (the one nearest at, or every placement).",
+        "type": "boolean"
+      },
+      "sound_id": {
+        "description": "A sound_id from search_sounds.",
+        "pattern": "^sfx_[a-f0-9]{16}$",
+        "type": "string"
+      }
+    },
+    "required": [
+      "sound_id"
+    ],
+    "type": "object"
+  },
+  "maxItems": 24,
+  "minItems": 1,
+  "type": "array"
+}

Changed3 schema fields changedOct 31, 2026
- changedInput schema / properties / camera_sound / 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 / camera_sound / properties / ranges / items / maxItems
```
Added value: +2
```
- addedInput schema / properties / camera_sound / properties / ranges / items / minItems
```
Added value: +2
```
AddedOct 31, 2026

TDQS

C2.6/5.0

Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description needed to explain what is destroyed or replaced (existing music, prior placements, camera audio), and it does not. The one genuinely additive detail is 'Cost: Free,' a pricing fact not present in annotations. For an 8-parameter mutation with nested objects, that is thin.

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 fragments with zero filler, and the enumeration comes first. It is efficient, though the fragmentary style reads as under-specification rather than disciplined concision, and no sentence is a full statement of purpose.

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

Completeness2/5

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

With 8 optional parameters, nested objects, destructive semantics and a version/operation-id model (base_version, operation_id, output_id), the description should explain at minimum that omitted groups are left unchanged and how retries/versions work. None of that is covered. An output schema exists, so return values needn't be described.

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 the nested music, camera_sound, house_sounds and sound_effects fields is already documented with units, ranges and defaults. The description's list of four audio domains loosely maps to those groups but adds no meaning, syntax, or interaction rules (e.g. music vs asset_id vs music_staging_key precedence). 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 is a noun-phrase list ('Music, exact sound effects, the style's own effects, and the footage sound') that mirrors the four property groups in the schema rather than stating an action; the verb has to be borrowed from the title 'Change the sound'. An agent can infer this is the audio-editing tool, but nothing distinguishes it from siblings like add_voiceover or the sound-related parts of add_clip.

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 explicit when-to-use or when-not-to-use guidance and no named alternative — for instance nothing says to use add_voiceover for narration or search_sounds first to find sound_ids. 'Cost: Free' is the only decision-relevant hint, and it speaks to pricing rather than to tool selection.

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?