Skip to main content
Glama

Change Speed

speed
Destructive

Change playback speed, or fast-forward ranges, and re-encode. Audio is retempo'd to match.

Instructions

Change playback speed, or fast-forward ranges, and re-encode. Audio is retempo'd to match.

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

Input Schema

NameRequiredDescriptionDefault
inputYesPath to the source video.
factorNoWhole clip: >1 faster, <1 slower.
outputNoOptional output path. Defaults under SCREENCAST_HOME/edits.
segmentsNoOr fast-forward just these ranges (audio shortened, not pitched).
overwriteNoAllow replacing an existing file at the output path (default false).

Output Schema

NameRequiredDescriptionDefault
outputPathYesPath of the file written.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.51.1
    • changedInput schema / properties / factor / description
      Previous value: -"Speed multiplier: >1 is faster, <1 is slower (e.g. 2 = double speed)."New value: +"Whole clip: >1 faster, <1 slower."
    • addedInput schema / properties / segments
      Added value: +{
      +  "description": "Or fast-forward just these ranges (audio shortened, not pitched).",
      +  "items": {
      +    "properties": {
      +      "end": {
      +        "exclusiveMinimum": 0,
      +        "type": "number"
      +      },
      +      "factor": {
      +        "exclusiveMinimum": 1,
      +        "maximum": 100,
      +        "type": "number"
      +      },
      +      "start": {
      +        "minimum": 0,
      +        "type": "number"
      +      }
      +    },
      +    "required": [
      +      "start",
      +      "end",
      +      "factor"
      +    ],
      +    "type": "object"
      +  },
      +  "minItems": 1,
      +  "type": "array"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "input",
      -  "factor"
      -]New value: +[
      +  "input"
      +]
  2. Changed1 schema field changedv0.47.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "outputPath": {
      +      "description": "Path of the file written.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "outputPath"
      +  ],
      +  "type": "object"
      +}
  3. First observedv0.32.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is largely covered. The description adds real context beyond them: the operation re-encodes and retempos the audio to stay in sync, which signals a lossy, potentially slow transformation. It does not explain what the destructive hint refers to (overwriting an existing output file) or how the overwrite flag gates that.

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 short sentences, front-loaded with the core action and with zero filler. The phrasing 'or fast-forward ranges' is slightly compressed, but nothing is wasted.

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 described, and the mutation semantics are partly covered by annotations. What is missing is a sentence tying destructiveHint to the overwrite behavior and the default output location, which matters for a write tool with five parameters.

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 100%, so every parameter is already documented in the schema; baseline is 3. The description's 'Audio is retempo'd to match' complements the schema's segments note ('audio shortened, not pitched'), but it adds no syntax, units, or constraints beyond what the fields already say.

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: change playback speed or fast-forward specified ranges, plus re-encoding. An agent can distinguish it from siblings like 'compress' or 'convert' because the operation is time-scaling, not format/quality work. It stops short of naming a sibling it is explicitly not, so a 4 rather than 5.

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?

The two-mode structure (whole-clip 'fast-forward ranges' vs. a single factor) is implied by the description and made concrete only by the schema's 'factor' and 'segments' fields. There is no explicit statement of when to choose segments over factor, no prerequisite guidance, and no alternatives named.

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