Cutible MCP Server

set_speed

Change a video clip's playback speed by specifying a speed factor, enabling precise control over clip timing in headless editing workflows.

Instructions

Set clip playback speed.

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": {
      "clip_id": "<clip_id>",
      "speed": "<speed>"
    },
    "name": "set_speed"
  }
}

Input Schema

Name	Required	Description	Default
`speed`	Yes
`clip_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 14, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It indicates a mutation ('Set') but does not say what happens to the clip's existing speed, whether the operation is reversible, whether duration is affected, or whether any validation or side effects occur.

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?

The description is a single, front-loaded sentence with no filler or redundant wording. Every word contributes to identifying the core operation, which is ideal for conciseness even though more behavioral context could be added elsewhere.

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

Completeness2/5

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

For a 2-parameter mutation tool with no annotations and no output schema, the description is too sparse. An agent lacks critical information about valid speed values, units, and what the tool does to the timeline or clip beyond changing a nominal speed property.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate by explaining parameter meanings. It does not clarify whether 'speed' is a multiplier, percentage, or absolute value, nor does it specify allowed ranges or the format of clip_id. The parameter names are minimally self-explanatory but insufficient for correct invocation.

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 uses a specific verb ('Set') and resource ('clip playback speed'), making the primary purpose clear. It does not explicitly contrast with sibling tools like set_volume, but the resource and property are unambiguous enough for an agent to distinguish the action.

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 gives no guidance on when to use this tool versus alternatives such as set_volume, trim, or add_transition. No context is provided about prerequisites, intended workflow position, or situations where a different speed-related operation would be more appropriate.

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