Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Set text motion

set_text_motion
Idempotent

Sets or replaces element-local position, scale, rotation and opacity curves on an existing ordinary text item. Empty or omitted motion clears explicit curves. Subject-matted text does not support this movement.

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": {
      "id": "<id>",
      "project_id": "<project_id>"
    },
    "name": "set_text_motion"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
motionNoElement-local motion curves. t is seconds from this text's own start; x/y are frame fractions, scale is relative, rotation is degrees, opacity is 0..1.
project_idYesExplicit project identifier for this request. The connection's navigation pointer does not select the target.
motion_motifNoActive Blueprint motion motif id this event executes; never 'hold'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / project_id / description
      Previous value: -"Required immutable scope for this call. Copy the id from list_projects/open_project/project_state; the active-project pointer is never used to guess."New value: +"Explicit project identifier for this request. The connection's navigation pointer does not select the target."
  2. 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"
+  }
+]
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare idempotent, non-read-only and non-destructive; the description adds the important disclosure that empty or omitted motion CLEARS explicit curves, which an agent would not know from annotations alone, plus the subject-matte restriction. It stops short of saying whether clearing is reversible or what happens to curves on axes not supplied in a partial motion object.

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?

Three short sentences, front-loaded with the verb and resource, then the clearing rule, then the exclusion. No filler, no restatement of the title, and each sentence carries a distinct fact.

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 nested-object mutation with no output schema, the description covers scope, replacement semantics, clearing behavior and the subject-matte exclusion, which is most of what an agent needs. It leaves partial-update semantics (does supplying only scale wipe x/y?) and the relationship between motion_motif and the curves unexplained.

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 75% and the nested motion object already documents t as seconds from the text's own start, x/y as frame fractions, scale as relative, rotation in degrees and opacity 0..1. The description's only real addition is the omission/clearing semantics for motion; it says nothing about project_id or motion_motif ('never hold') beyond what the schema notes, so a baseline 3 is appropriate.

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?

Names a specific verb ('sets or replaces') and the exact resource (element-local position, scale, rotation, opacity curves on an existing ordinary text item). It scopes who it applies to ('ordinary text item', not subject-matted text), which distinguishes it from the many motion-adjacent siblings, but it never names which sibling (e.g. set_overlay_motion, set_motion_graphic) an agent should pick for non-text elements.

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?

Gives one explicit exclusion ('Subject-matted text does not support this movement') and implies the precondition of an existing text item, but offers no positive when-to-use routing against the ~200 siblings that also mutate motion. An agent still has to infer the boundary between this and set_overlay_motion / set_motion_graphic.

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

All Valmera — 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