agent-video-engine

Overview Schema Source Related Servers Discussions Admin

revision_restore

Restore a saved revision as a new revision while preserving history and original footage, using expected revision checks to prevent overwriting newer edits.

Instructions

Restore a saved revision as a new revision. Keeps history and original footage.

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": {
      "projectDir": "<projectDir>",
      "expectedRevision": "<expectedRevision>",
      "revision": "<revision>"
    },
    "name": "revision_restore"
  }
}

Input Schema

Name	Required	Description
`revision`	Yes
`projectDir`	Yes	Absolute path of the local video project directory
`expectedRevision`	Yes	Revision returned by project_inspect. Prevents overwriting newer edits.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.0.0Nov 6, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false. The description usefully reinforces and explains that non-destructive posture ('Keeps history and original footage'), which is real added context. However it says nothing about the expectedRevision concurrency guard, failure modes, or what happens if the revision no longer exists.

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?

Two tight sentences, front-loaded with the action, no redundant or filler wording.

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 mutating, 3-required-param tool with no output schema, the definition covers the core action and its non-destructive nature but omits what the call returns (presumably the new revision number) and what the agent should do after restoring.

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 67%, with projectDir and expectedRevision documented in-schema but 'revision' undocumented. The description implies 'revision' is an existing saved revision being restored ('a saved revision'), adding a little meaning, but it gives no hint about the optimistic concurrency check that expectedRevision performs or how to obtain it.

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?

Specific verb+resource: 'Restore a saved revision as a new revision' tells the agent exactly what happens and that the result is itself a revision. It distinguishes itself adequately from revision_list/revision_compare, though it does not name those siblings explicitly.

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?

Usage is only implied: an agent can infer this is the tool for reverting to an earlier state, but the description never states when to prefer it over revision_compare (inspect before restoring) or how it relates to draft_apply. No exclusions or prerequisites such as needing a valid revision from revision_list.

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