Clueso

Set voice

set_voice

Set the voiceover voice for every clip in a project, or only for the clips in clip_ids.

Use this to apply a clueprint's voice (read voiceover.voice.name and voiceover.voice.engine from the clueprint source data), or to switch all clips to a specific voice in one call. When the user names specific clips, pass their ids in clip_ids so the other clips keep their voice. The voice is looked up by name + engine; lookup is case-insensitive on the name.

Common engines: 'eleven' (ElevenLabs), 'cartesia', 'google'.

ElevenLabs voices use the latest voice generation unless voice_version says otherwise. Leave it unset; pass "legacy" ONLY when the user explicitly asks for the legacy/older voice generation.

Input Schema

TableJSON Schema

Name	Required	Description
`clip_ids`	No	Clip ids to change the voice on. Omit to change EVERY clip in the project.
`project_id`	Yes	The project (guide) ID
`voice_name`	Yes	Voice name as stored in the voices table (e.g. 'Alex', 'Sofia')
`voice_engine`	Yes	Voice engine — 'eleven', 'cartesia', 'google', etc.
`voice_version`	No	ElevenLabs voice generation. Leave unset (latest). Use 'legacy' ONLY when the user explicitly asks for the legacy/older voice generation; never choose it yourself. Ignored for non-ElevenLabs voices.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 8, 2026

addedInput schema / properties / clip_ids

Added value: +{
+  "description": "Clip ids to change the voice on. Omit to change EVERY clip in the project.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / voice_version

Added value: +{
+  "description": "ElevenLabs voice generation. Leave unset (latest). Use 'legacy' ONLY when the user explicitly asks for the legacy/older voice generation; never choose it yourself. Ignored for non-ElevenLabs voices.",
+  "enum": [
+    "latest",
+    "legacy"
+  ],
+  "type": "string"
+}

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",
-  "voice_name",
-  "voice_engine",
-  "context",
-  "llm_model"
-]New value: +[
+  "project_id",
+  "voice_name",
+  "voice_engine"
+]

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",
-  "voice_name",
-  "voice_engine"
-]New value: +[
+  "project_id",
+  "voice_name",
+  "voice_engine",
+  "context",
+  "llm_model"
+]

Changed2 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
```

First observedAug 11, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With annotations already declaring readOnlyHint=false, destructiveHint=false, and openWorldHint=false, the description adds meaningful behavioral context: omitted clip_ids changes every clip, lookup is by name + engine and case-insensitive, and voice_version defaults to latest with legacy reserved for explicit user requests. It does not discuss permissions or rate limits, but the safety profile is otherwise clear.

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 description is front-loaded with the core action and scope, then layers in mapping, lookup, engines, and version guidance. It is somewhat longer than necessary and repeats a few schema details, but each paragraph adds useful operational context for a multi-parameter mutation tool.

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

Completeness5/5

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

For a five-parameter mutation tool with no output schema, the description covers scope, clip targeting, lookup behavior, common engines, and voice-version defaults. An agent has enough information to invoke it correctly in the intended scenarios.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all five parameters, but the description adds non-obvious semantics: case-insensitive voice lookup, common engine values, and the default/latest behavior of voice_version plus its non-ElevenLabs irrelevance. This goes beyond merely restating the schema.

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?

The description states a specific verb and resource ('Set the voiceover voice for every clip in a project, or only for the clips in clip_ids'), making the action clear. It does not name or distinguish itself from sibling tools such as voiceover_batch or update_audio, so it stops short of full sibling differentiation.

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?

It gives clear usage contexts: applying a clueprint's voice or switching all clips in one call, and it explains when to pass clip_ids so other clips keep their voice. It does not explicitly state when-not-to-use or name alternative tools, so it lacks the full when/when-not/alternatives framing.

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.

Set voice

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources