Valmera — AI Video Editor

Add vector graphic

add_vector_graphic

Adds a renderer-native rectangle, ellipse, line, arrow, ring or progress graphic over a program-time window. Geometry uses frame fractions; palette, stroke, rounding and element-local motion are configurable.

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": {
      "kind": "<kind>",
      "start": "<start>",
      "end": "<end>",
      "project_id": "<project_id>"
    },
    "name": "add_vector_graphic"
  }
}

Input Schema

Name	Required	Description
`x`	No
`y`	No
`end`	Yes
`kind`	Yes
`color`	No
`start`	Yes
`value`	No
`width`	No
`height`	No
`motion`	No	Element-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.
`opacity`	No
`rounding`	No
`project_id`	Yes	Explicit project identifier for this request. The connection's navigation pointer does not select the target.
`motion_motif`	No	Active Blueprint motion motif id this event executes; never 'hold'.
`stroke_color`	No
`stroke_width`	No
`background_color`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

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."

Changed5 schema fields changedOct 9, 2026

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"
+  }
+]

First observedSep 9, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world mutation, so the safety profile is covered. The description adds useful conceptual context — 'renderer-native', frame-fraction geometry, and element-local motion — but says nothing about what happens on repeat calls despite idempotentHint=false, or whether adding a graphic conflicts with existing overlays.

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?

Two dense sentences with no filler, and the primary purpose is front-loaded before the geometry/config details. The trade-off is that terseness contributes to the parameter gaps, but the prose itself is well-structured.

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

Completeness2/5

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

A 17-parameter mutation tool with a nested motion object, no output schema and 18% schema coverage needs far more description than two sentences. The motion curve format (t/v/ease, up to 24 keyframes), the project_id targeting rule, and how 'value' interacts with the ring/progress kinds are all left undocumented.

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?

With schema description coverage at only 18%, the description has to carry weight, and it does explain the coordinate system (frame fractions), the program-time window for start/end, and that palette, stroke, rounding and motion are configurable. But key parameters are untouched: 'value' (presumably the progress fill), width/height, opacity vs the motion opacity curve, background_color, and motion_motif, which is only defined inside the schema.

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?

States a specific verb and resource ('Adds a renderer-native rectangle, ellipse, line, arrow, ring or progress graphic') and names the enumerated shape kinds, so an agent knows exactly what gets created. It does not differentiate from near-siblings such as add_motion_graphic, add_element, or set_vector_graphic, leaving the agent to infer which add-family tool to pick.

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

Usage Guidelines2/5

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

The only contextual hint is 'over a program-time window', which implies timeline placement but never states when to use this versus add_motion_graphic or add_element, nor when to use set_vector_graphic to modify an existing one instead. No prerequisites, no when-not conditions, and no mention that a project_id must be supplied because the navigation pointer is ignored.

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