CutClip.one

voice.compile

Preview what voice.generate would speak for a voice placeholder — text, voice, model and 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": {
      "projectId": "<projectId>",
      "placeholderId": "<placeholderId>"
    },
    "name": "voice.compile"
  }
}

Input Schema

Name	Required	Description
`text`	No	The words to speak. Defaults to the clip's prompt, then the scene's voice prompt
`model`	No	eleven-multilingual-v2 (default), eleven-v3 (most expressive) or eleven-flash-v2.5 (cheapest)
`voiceId`	No	ElevenLabs voice (voice.list). Defaults to characterId's voice, then a narrator voice
`projectId`	Yes
`characterId`	No	Speak in this character's voice
`placeholderId`	Yes	A voice placeholder on an audio track (timeline.add_placeholder with kind voice)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations present, the description carries the burden and does well: it discloses this is a non-mutating preview, that it returns text/voice/model/cost, and critically that it is 'Free' — billing behavior an agent would otherwise have to guess at in a credit-based studio. It omits whether the placeholder must pre-exist or what errors look like.

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?

A single em-dash-separated sentence with the relationship to voice.generate front-loaded and the cost signal trailing. Every clause earns its place; nothing is padded.

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 six-parameter, two-required preview tool with 83% schema coverage and no output schema, the description supplies what matters: the return contents (text, voice, model, cost) and the free/no-side-effect guarantee. Only error and precondition behavior is unaddressed.

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 83%, so the schema already documents nearly every parameter, including defaults and model options. The description only echoes the resolved fields (text, voice, model, cost) without adding format or precedence detail beyond the schema's 'Defaults to the clip's prompt, then the scene's voice prompt'.

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?

States a specific verb (preview) and resource (voice placeholder speech), and explicitly frames itself relative to voice.generate. An agent can immediately distinguish this dry-run from the actual generation sibling without opening either schema.

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 'preview what voice.generate would speak' framing plus 'Free' strongly signals the use case: inspect before spending credits. It does not explicitly say when not to use it or name voice.list as an alternative for voice resolution, but the context is clear.

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

All CutClip.one 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.