Vidova

Make what an effect needs

prepare_effect

Make what an effect already in the film still needs, and link it in: its person mask or its face. read_film lists the effects that wait for something under Effects waiting, with what each one needs. It links a mask or a face made before when one covers the seconds the effect plays over, else runs cutout_subject or track_faces there, which use credits as those tools do; a run already going for it is joined, not started or charged again. A photo or footage the effect needs is named for you to set, not guessed. clipId is the effect's clip id. A long cutout answers with a Job ID: wait for it with wait_for_jobs. Check the result with preview_frame.

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": {
      "clipId": "<clipId>",
      "projectId": "<projectId>"
    },
    "name": "prepare_effect"
  }
}

Input Schema

Name	Required	Description	Default
`clipId`	Yes	Id of the effect's clip in the film, from read_film's Effects waiting.
`projectId`	Yes	The 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.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 19, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Adds substantial behavior beyond the annotations: credits are consumed 'as those tools do', an in-flight run 'is joined, not started or charged again', a long cutout returns a Job ID that must be awaited, and photo/footage requirements are surfaced rather than guessed. These are exactly the cost, idempotency and follow-up facts an agent needs before invoking a non-readOnly 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?

Front-loaded with the action and its dependency, then flows into sourcing, cost and follow-up semantics in roughly priority order. It is dense and semicolon-heavy, but no sentence is filler and every clause carries distinct information.

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?

With no output schema, the description still covers the return contract ('a long cutout answers with a Job ID'), the async follow-up (wait_for_jobs), and result verification (preview_frame). Nothing an agent needs to call this correctly appears to be missing.

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 100%, so both clipId and projectId are already documented in the schema (including which project is used when null). The description only restates that clipId is the effect's clip id and never mentions projectId, adding negligible meaning over the structured data. Baseline 3 applies.

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?

Names a specific verb ('make ... and link it in') and a concrete resource: the person mask or face an effect already in the film is waiting on. It is clearly distinguished from the lower-level siblings it may invoke (cutout_subject, track_faces) by being the orchestrator that resolves the effect's dependency.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('read_film lists the effects that wait for something under Effects waiting'), the default path (link a pre-existing mask/face when it covers the effect's seconds) and the fallback (otherwise run cutout_subject or track_faces there). It even states the next step for long jobs (wait_for_jobs) and verification (preview_frame).

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

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