Skip to main content
Glama

clip_properties

Get or set Inspector properties of timeline clips, such as pan, zoom, opacity, crop, composite, retime, and audio levels, to adjust clip appearance and sound without keyframes.

Instructions

Get or set Inspector properties of timeline clips. Friendly keys: x, y (pan/tilt px), zoom (1.0=100%), rotation, opacity (0-100), anchor_x/y, flip_x/y, crop_left/right/top/bottom (px), crop_softness, composite (normal|screen|multiply|overlay|add|soft_light|…), dynamic_zoom (bool) + dynamic_zoom_ease (linear|in|out|in_and_out), retime (nearest|frame_blend|optical_flow), motion_estimation, scaling (crop|fit|fill|stretch), resize_filter, volume (dB −100..30), audio_pan (−100..100), pitch_semitones, voice_isolation (bool) + voice_isolation_amount, dialogue_leveler … Raw Resolve keys (ZoomX, Pan, …) also work. Values are static (no keyframes via API).

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": {
      "clips": "<clips>"
    },
    "name": "clip_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
setNo
clipsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add real behavioral context: value ranges (zoom 1.0=100%, volume in dB, audio_pan range), accepted enum domains, and the constraint that values are static with no keyframes. It omits what happens with invalid or raw keys, whether a project/timeline must be open, and what a read returns.

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?

The core action is front-loaded and the key list is dense but purposeful, essentially a compact reference table with ranges and allowed values. The trailing note about raw Resolve keys is short and earns its place; the long enumeration is justified by the 0% schema coverage.

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 tool that reads and writes dozens of properties with no annotations and no output schema, the property surface is well covered. Missing pieces are the identifier format for `clips` and any sense of what a read returns, which matters given the 'get' mode has no output schema to fall back on.

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 0%, so the description must compensate. The long friendly-key list effectively documents the contents of the `set` dictionary, which is valuable. But the required `clips` parameter gets no explanation of expected format (IDs, names, indices, single vs list), and the get-vs-set behavior of omitting `set` is only implied by 'Get or set'.

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 pair and resource: 'Get or set Inspector properties of timeline clips.' An agent can tell it touches clip properties. It does not, however, distinguish itself from nearby siblings like clip_update, clip_info, or clip_speed, so a reader must infer why this tool exists alongside them.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no routing to alternatives such as clip_update or clip_info. The only conditional hint is that values are static and keyframes are unavailable, which is a limitation rather than usage direction.

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