Skip to main content
Glama

Vidova

by ai.vidova
OverviewDiscussionsAdmin

Move, scale or inset an object track

offset_track

Move, scale or inset an object track's corners on every frame: e.g. from a sign's outer frame to its inner panel with inset 0.04, so a pinned picture sits inside the border. scale and inset are in the surface's own UV and go through its perspective on each frame, so the far side moves less than the near side. shift moves it in source pixels or in surface UV. newLabel keeps the original and writes a new track. The answer ends with the track's new quality verdict and flagged ranges, and a preview_range call with overlays ["tracks"] that shows the changed frames on the film: run it to check. Free.

Input Schema

NameRequiredDescriptionDefault
insetYesUV taken off each side of the surface: 0.04 moves every corner 4% of the surface's width and height inward, onto a sign's inner panel inside its border. Negative grows it outward. null is 0.
rangeYes[from, to] seconds to change (atSpace says what they are). null changes every frame.
scaleYesThe surface's size around its centre, in its own UV: 0.9 is 90%, 1.1 is 110%. null keeps the size.
shiftYes[dx, dy] added to every corner, in shiftSpace. null moves nothing.
clipIdYesThe film clip that plays this asset, when space or atSpace needs one and several clips play it. null picks the clip that shows the asset at that time.
atSpaceYesWhat this call's times are. null or source: seconds into the asset file. timeline: seconds of the film, read through the clip that plays the asset then (clipId to pick one).
trackIdYesThe object track id, as the tracking tool printed it or search_assets lists it (objectTracks).
newLabelYesnull changes the track itself. A label writes the result as a new track with its own id and keeps the original, e.g. "sign panel" for the inner panel beside the sign's outer frame.
projectIdYesThe project this call runs on without changing the open project. null (or leaving it out) uses the open project. wait_for_jobs takes the projectId of the calls that started the jobs.
shiftSpaceYesWhat shift is in. null or source: pixels of the asset. surface: UV of the tracked surface, where 1 is its whole width or height, so [0, 0.1] moves it down a tenth of its own height, in perspective.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say readOnly=false, destructive=false, idempotent=false; the description adds the important semantics: null newLabel mutates the track in place while a label forks a new track and keeps the original. It also discloses the response contents (quality verdict, flagged ranges) and that the call is free.

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?

Front-loaded with the verb and scope, then geometry, then the newLabel fork, then the verification step and cost. Every sentence contributes a distinct fact with no restatement of the name or title.

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

Completeness5/5

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

Ten required parameters and no output schema, yet the description explains the result payload and prescribes a check step, and covers the perspective/UV behavior that makes these parameters non-obvious. Nothing an agent needs to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the schema carries the baseline; the description still adds meaning by explaining that scale and inset operate in surface UV and pass through the surface's perspective, so the far side moves less than the near side. That geometric nuance is not fully in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb set (move, scale, inset) applied to a specific resource (an object track's corners on every frame). The inset/outer-frame-to-inner-panel example makes the effect unambiguous and separates it from siblings like edit_track or smooth_track.

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

Usage Guidelines4/5

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

Gives a clear when-to-use scenario and a recommended verification step (preview_range with overlays ["tracks"]), which is real usage guidance. It never names an alternative tool or an exclusion, so an agent must infer when edit_track or smooth_track is the better choice.

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

All Vidova toolsInspect
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