Valmera — AI Video Editor

Shape music

shape_music

Adjusts a supplied track's offset, window, fades, filtering and selected stutters to align a drop or other musical event with a program moment. Optional holds add a preceding silent interval.

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": {
      "project_id": "<project_id>"
    },
    "name": "shape_music"
  }
}

Input Schema

Name	Required	Description
`hold_s`	No
`payoff`	No
`dry_run`	No
`music_id`	No
`project_id`	Yes	Explicit project identifier for this request. The connection's navigation pointer does not select the target.
`stutter_at`	No
`intro_filter`	No
`stutter_beats`	No
`stutter_slice`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

changedInput schema / properties / project_id / description

Previous value: -"Required immutable scope for this call. Copy the id from list_projects/open_project/project_state; the active-project pointer is never used to guess."New value: +"Explicit project identifier for this request. The connection's navigation pointer does not select the target."

AddedOct 15, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent edit, and the description adds useful detail about what is altered (offset, window, fades, filter, stutters) and that holds insert a preceding silent interval. It does not disclose the non-idempotent consequence (repeated calls compound on the same track), whether edits replace or layer on prior shaping, or what dry_run does, which is the key safety lever for a mutation tool.

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 that front-load the operation and follow with the secondary 'holds' behavior. No filler, though the clause 'and selected stutters' and 'or other musical event' are slightly loose where a crisper enumeration would read better.

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?

For a 9-parameter mutation tool with no output schema and near-zero schema descriptions, the description covers the conceptual surface but leaves dry_run, payoff, and music_id resolution unexplained, and says nothing about what is returned or how success is confirmed. Adequate to start, not adequate to call confidently in one pass.

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 only 11% (just project_id), so the description carries most of the burden, and it does map loosely onto hold_s, stutter_*, intro_filter, and 'supplied track' for music_id. But two important parameters, dry_run and payoff, get no explanation at all, and no units, ranges, or default behavior are given for offsets and windows beyond the schema's own min/max.

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 names a specific verb ('Adjusts') and a specific resource ('a supplied track'), then enumerates exactly which properties are touched (offset, window, fades, filtering, stutters) and the goal (aligning a drop with a program moment). It is clear what the tool does without opening the schema, though it never names a sibling such as set_music_fit, swap_music, or plan_to_music to mark the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the phrase 'to align a drop or other musical event with a program moment', which tells an agent the scenario this tool serves. However, there is no explicit when-not guidance and no routing against the many adjacent music tools (add_music, swap_music, set_music_fit, plan_to_music), so the agent must infer the choice.

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

All Valmera — AI Video Editor 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.