Clypmint

Add a voice-over

add_voiceover

DestructiveIdempotent

Narrate a script from a second (a vo_ layer). Cost: 1 credit a started minute of voice-over.

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": {
      "script": "<script>",
      "voice": "<voice>",
      "at": "<at>"
    },
    "name": "add_voiceover"
  }
}

Input Schema

Name	Required	Description
`at`	Yes	Film second it starts.
`voice`	Yes	A narrator (get_guide voice).
`script`	Yes	The words, read exactly.
`captions`	No	Caption its words.
`video_id`	No	Video; the open one if left out.
`base_version`	No	Version id you read.

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.

AddedNov 7, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=true, idempotentHint=true, openWorldHint=true). The description adds a genuinely useful non-annotation detail — the 1-credit-per-started-minute cost. However it does not explain what the destructive hint means here, e.g. whether an existing vo_ layer or overlapping audio at that second is overwritten.

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 tight sentences with no filler, and the core action is front-loaded ahead of the cost note. The phrasing 'from a second' is slightly cryptic but the schema clarifies it.

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?

An output schema exists, so return values need not be explained, and the cost note covers the main operational concern. Still, for a destructive mutation that writes a new layer onto the timeline, it omits what happens to existing content at that second and any prerequisite for resolving the voice via get_guide.

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 all six parameters, including the voice/get_guide reference and the at second, are already documented in the schema. The description adds no syntax or format detail beyond that, so the baseline of 3 applies.

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?

States a specific verb and resource: it narrates a script as a voice-over layer ('vo_ layer'). That clearly distinguishes it from sibling tools like add_clip or put_overlay, though it never names an alternative explicitly.

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?

The description describes what the tool does but gives no when-to-use versus when-not guidance and names no alternative tools. The only implied context is that a script is narrated onto a video at a given second.

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?