Skip to main content
Glama

Valmera — agentic AI video editor

by io.valmera
OverviewDiscussionsAdmin

Set overlay motion

set_overlay_motion
Idempotent

PROJECT-SCOPED: this call acts only on the explicit project_id and returns the project identity with its result. Author or replace x/y/scale/rotation/opacity on an EXISTING visual overlay using scalars or element-local keyframes. This is the general motion-graphics primitive for logos, images and PIP clips: one coherent move can drift, push, overshoot, rotate and fade without stacking named presets. Keyframe t=0 is the overlay's own start, not program time. A scalar makes that property static. Full-frame B-roll covers ignore x/y/scale; screen takeovers own their tracked camera geometry and reject ordinary curves.

Input Schema

NameRequiredDescriptionDefault
idYes
motionYesElement-local visual-overlay curves. t is seconds from the overlay's own start; x/y and scale are frame fractions, rotation is degrees, opacity is 0..1.
project_idYesRequired immutable scope for this call. Copy the id from list_projects/open_project/project_state; the active-project pointer is never used to guess.
motion_motifNoActive Blueprint motion motif id this event executes; never 'hold'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / motion / properties / opacity / anyOf
      Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "items": {
-      "properties": {
-        "ease": {
-          "enum": [
-            "linear",
-            "in",
-            "out",
-            "in_out",
-            "hold"
-          ],
-          "type": "string"
-        },
-        "t": {
-          "type": "number"
-        },
-        "v": {
-          "type": "number"
-        }
-      },
-      "required": [
-        "t",
-        "v"
-      ],
-      "type": "object"
-    },
-    "minItems": 1,
-    "type": "array"
-  }
-]New value: +[
+  {
+    "type": "number"
+  },
+  {
+    "items": {
+      "properties": {
+        "ease": {
+          "enum": [
+            "linear",
+            "in",
+            "out",
+            "in_out",
+            "hold"
+          ],
+          "type": "string"
+        },
+        "t": {
+          "minimum": 0,
+          "type": "number"
+        },
+        "v": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "t",
+        "v"
+      ],
+      "type": "object"
+    },
+    "maxItems": 24,
+    "minItems": 1,
+    "type": "array"
+  }
+]
    • changedInput schema / properties / motion / properties / rotation / anyOf
      Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "items": {
-      "properties": {
-        "ease": {
-          "enum": [
-            "linear",
-            "in",
-            "out",
-            "in_out",
-            "hold"
-          ],
-          "type": "string"
-        },
-        "t": {
-          "type": "number"
-        },
-        "v": {
-          "type": "number"
-        }
-      },
-      "required": [
-        "t",
-        "v"
-      ],
-      "type": "object"
-    },
-    "minItems": 1,
-    "type": "array"
-  }
-]New value: +[
+  {
+    "type": "number"
+  },
+  {
+    "items": {
+      "properties": {
+        "ease": {
+          "enum": [
+            "linear",
+            "in",
+            "out",
+            "in_out",
+            "hold"
+          ],
+          "type": "string"
+        },
+        "t": {
+          "minimum": 0,
+          "type": "number"
+        },
+        "v": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "t",
+        "v"
+      ],
+      "type": "object"
+    },
+    "maxItems": 24,
+    "minItems": 1,
+    "type": "array"
+  }
+]
    • changedInput schema / properties / motion / properties / scale / anyOf
      Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "items": {
-      "properties": {
-        "ease": {
-          "enum": [
-            "linear",
-            "in",
-            "out",
-            "in_out",
-            "hold"
-          ],
-          "type": "string"
-        },
-        "t": {
-          "type": "number"
-        },
-        "v": {
-          "type": "number"
-        }
-      },
-      "required": [
-        "t",
-        "v"
-      ],
-      "type": "object"
-    },
-    "minItems": 1,
-    "type": "array"
-  }
-]New value: +[
+  {
+    "type": "number"
+  },
+  {
+    "items": {
+      "properties": {
+        "ease": {
+          "enum": [
+            "linear",
+            "in",
+            "out",
+            "in_out",
+            "hold"
+          ],
+          "type": "string"
+        },
+        "t": {
+          "minimum": 0,
+          "type": "number"
+        },
+        "v": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "t",
+        "v"
+      ],
+      "type": "object"
+    },
+    "maxItems": 24,
+    "minItems": 1,
+    "type": "array"
+  }
+]
    • changedInput schema / properties / motion / properties / x / anyOf
      Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "items": {
-      "properties": {
-        "ease": {
-          "enum": [
-            "linear",
-            "in",
-            "out",
-            "in_out",
-            "hold"
-          ],
-          "type": "string"
-        },
-        "t": {
-          "type": "number"
-        },
-        "v": {
-          "type": "number"
-        }
-      },
-      "required": [
-        "t",
-        "v"
-      ],
-      "type": "object"
-    },
-    "minItems": 1,
-    "type": "array"
-  }
-]New value: +[
+  {
+    "type": "number"
+  },
+  {
+    "items": {
+      "properties": {
+        "ease": {
+          "enum": [
+            "linear",
+            "in",
+            "out",
+            "in_out",
+            "hold"
+          ],
+          "type": "string"
+        },
+        "t": {
+          "minimum": 0,
+          "type": "number"
+        },
+        "v": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "t",
+        "v"
+      ],
+      "type": "object"
+    },
+    "maxItems": 24,
+    "minItems": 1,
+    "type": "array"
+  }
+]
    • changedInput schema / properties / motion / properties / y / anyOf
      Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "items": {
-      "properties": {
-        "ease": {
-          "enum": [
-            "linear",
-            "in",
-            "out",
-            "in_out",
-            "hold"
-          ],
-          "type": "string"
-        },
-        "t": {
-          "type": "number"
-        },
-        "v": {
-          "type": "number"
-        }
-      },
-      "required": [
-        "t",
-        "v"
-      ],
-      "type": "object"
-    },
-    "minItems": 1,
-    "type": "array"
-  }
-]New value: +[
+  {
+    "type": "number"
+  },
+  {
+    "items": {
+      "properties": {
+        "ease": {
+          "enum": [
+            "linear",
+            "in",
+            "out",
+            "in_out",
+            "hold"
+          ],
+          "type": "string"
+        },
+        "t": {
+          "minimum": 0,
+          "type": "number"
+        },
+        "v": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "t",
+        "v"
+      ],
+      "type": "object"
+    },
+    "maxItems": 24,
+    "minItems": 1,
+    "type": "array"
+  }
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, but the description goes further: it discloses project scoping ('acts only on the explicit project_id and returns the project identity'), the replacement behavior ('Author or replace'), the keyframe origin ('t=0 is the overlay's own start, not program time'), and the fact that some overlay types reject ordinary curves. That is meaningful context beyond the annotations, though permission requirements are unstated.

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 scoping constraint is front-loaded in caps, and each sentence carries distinct information, but the middle sentences are long and dense enough to slow parsing slightly. No filler or redundant restatement of the name is present.

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

Completeness4/5

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

For a mutation tool with no output schema, the description covers scope, return identity, keyframe semantics, static-scalar behavior and type-specific rejection rules. It stops short of stating permission prerequisites or exactly how overriding existing curves behaves, which are the remaining gaps.

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 75%, so the schema already documents most fields, but the description adds the crucial scalar-vs-keyframe duality ('A scalar makes that property static') and clarifies the temporal origin of keyframes. It leaves motion_motif and id unelaborated, so it adds value without fully compensating for the remaining gap.

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?

The description names a specific verb ('Author or replace') and resource ('x/y/scale/rotation/opacity on an EXISTING visual overlay'), and it positions the tool as 'the general motion-graphics primitive for logos, images and PIP clips', which differentiates it from the many set_* siblings. An agent can distinguish it from set_motion_graphic, set_text_motion, and move_overlay without opening any schema.

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?

It gives clear usage context ('general motion-graphics primitive for logos, images and PIP clips') and implicit exclusions ('Full-frame B-roll covers ignore x/y/scale; screen takeovers own their tracked camera geometry and reject ordinary curves'). However, it never names the sibling tool to use instead when the target is a text element or a screen takeover, leaving the agent to infer the routing.

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

All Valmera — agentic AI video editor 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