Clueso

Update an existing audio track

update_audio

Mutate fields on an existing music/SFX track by id. Read existing tracks via get_project.audio_tracks — the per-entry shape there matches this tool's args, so you can flip a knob (volume, fades, timing, loop) and write it back without losing the track's id.

Only fields you pass are changed; omitted fields are preserved. To delete a track entirely, use remove_from_project(target='audio') instead.

Input Schema

TableJSON Schema

Name	Required	Description
`loop`	No	Whether the track loops
`volume`	No	New playback volume 0-100
`fade_in`	No	Fade-in duration (seconds)
`fade_out`	No	Fade-out duration (seconds)
`music_id`	Yes	ID of the audio track (from get_project.audio_tracks[].id)
`project_id`	Yes	The project ID
`guide_end_time`	No	New end time on the project timeline (seconds)
`music_end_time`	No	New end offset within the source file (seconds)
`guide_start_time`	No	New start time on the project timeline (seconds)
`music_start_time`	No	New start offset within the source file (seconds)

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 22, 2026

removedInput schema / properties / context

Removed value: -{
-  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
-  "type": "string"
-}

removedInput schema / properties / conversation_id

Removed value: -{
-  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
-  "type": "string"
-}

removedInput schema / properties / llm_model

Removed value: -{
-  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "project_id",
-  "music_id",
-  "context",
-  "llm_model"
-]New value: +[
+  "project_id",
+  "music_id"
+]

Changed4 schema fields changedSep 22, 2026

addedInput schema / properties / context

Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}

addedInput schema / properties / conversation_id

Added value: +{
+  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
+  "type": "string"
+}

addedInput schema / properties / llm_model

Added value: +{
+  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "project_id",
-  "music_id"
-]New value: +[
+  "project_id",
+  "music_id",
+  "context",
+  "llm_model"
+]

Changed3 schema fields changedSep 17, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / loop / anyOf

Previous value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "enum": [
-      "true",
-      "false",
-      "1",
-      "0",
-      "yes",
-      "no"
-    ],
-    "type": "string"
-  }
-]New value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "enum": [
+      "0",
+      "1",
+      "true",
+      "false",
+      "yes",
+      "no"
+    ],
+    "type": "string"
+  }
+]

First observedAug 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already mark this as a mutation (readOnlyHint: false, destructiveHint: false), and the description adds genuine value beyond that: the partial-update semantics ('Only fields you pass are changed; omitted fields are preserved') and the id-preservation pattern. No contradiction with annotations — the 'Mutate' wording aligns with the non-readonly hint.

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

Conciseness5/5

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

Two tight paragraphs with zero filler. The purpose is front-loaded in the first sentence, and the second paragraph delivers only the two critical facts: partial-update behavior and the deletion alternative. Every sentence earns its place.

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?

For a mutation tool with 10 params, no output schema, and 2 required fields, the description covers the essential operational context: how to obtain track data, what gets preserved, and what not to use it for. It is complete enough for an agent to call it correctly; return-value details are reasonably omitted given no output schema exists.

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 coverage is 100%, so every one of the 10 parameters already carries a description in the schema. The description adds the useful note that the arg shape matches get_project.audio_tracks entries, which helps an agent populate fields, but it doesn't add per-parameter detail — the baseline of 3 for high schema coverage is appropriate.

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?

The description opens with 'Mutate fields on an existing music/SFX track by id' — a specific verb, resource, and identification method. It clearly distinguishes from add_audio (creation) and remove_from_project (deletion) by name, so an agent can differentiate without opening sibling schemas.

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 description tells the agent to read existing tracks via get_project.audio_tracks and notes the per-entry shape matches the tool's args, establishing the read-then-write workflow. It also gives an explicit exclusion for deletion via remove_from_project(target='audio'). It doesn't contrast with update_clips, but the audio/clip domain split is clear enough from names.

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

All Clueso 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.

Update an existing audio track

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources