Sequencer

update_overlay_item

Update an existing overlay item. Can change text, position, timing, animation, opacity, and more.

Input Schema

Name	Required	Description
`exit`	No	Exit animation, or null to remove
`size`	No	Normalized overlay size
`text`	No	New text content
`type`	No	Change item type when also supplying compatible fields
`color`	No	New text color (hex or rgba)
`enter`	No	Entrance animation, or null to remove
`width`	No	Legacy shorthand for size.width
`border`	No	Border styling, or null to remove
`editId`	Yes	The edit ID
`height`	No	Legacy shorthand for size.height
`itemId`	Yes	The overlay item ID
`shadow`	No	Media overlay drop shadow, or null to remove
`volume`	No	Video overlay audio volume
`clipEnd`	No	Video overlay trim end in seconds, or null to clear
`mediaId`	No	MediaDocV2 ID for image/video overlays, or null to remove
`opacity`	No	Opacity from 0 to 1
`trackId`	Yes	The overlay track ID
`duration`	No	Timeline duration in seconds
`fontSize`	No	New font size
`position`	No	Normalized overlay position
`rotation`	No	Rotation in degrees
`clipStart`	No	Video overlay trim start in seconds
`fontStyle`	No	New font style
`keyframes`	No	Transform keyframes relative to item start
`positionX`	No	Legacy shorthand for position.x
`positionY`	No	Legacy shorthand for position.y
`speedRamp`	No	Variable speed curve for video overlays, or null to clear
`startTime`	No	Timeline start time in seconds
`textAlign`	No	New text alignment
`fontFamily`	No	New font family
`fontWeight`	No	New font weight
`lineHeight`	No	New line-height multiplier
`lineStyles`	No	Per-line text style overrides
`textConfig`	No	Full TextEffectConfig partial update
`strokeColor`	No	New text stroke color
`strokeWidth`	No	New text stroke width
`workspaceId`	Yes	The workspace ID
`borderRadius`	No	Corner radius in 720p logical pixels
`letterSpacing`	No	New letter spacing
`playbackSpeed`	No	Flat playback speed for video overlays
`textAnimation`	No	New text animation
`remotionConfig`	No	Update animation code or editable settings, merged with the existing composition
`textShadowBlur`	No	New text shadow blur
`backgroundColor`	No	New text background color
`textShadowColor`	No	New text shadow color
`textShadowOffsetX`	No	New text shadow horizontal offset
`textShadowOffsetY`	No	New text shadow vertical offset
`backgroundPaddingX`	No	New text background horizontal padding
`backgroundPaddingY`	No	New text background vertical padding
`backgroundBorderRadius`	No	New text background corner radius

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 9, 2026

changedInput schema / properties / speedRamp / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "curve": {
-        "items": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "number"
-          },
-          {
-            "type": "number"
-          },
-          {
-            "type": "number"
-          }
-        ],
-        "maxItems": 4,
-        "minItems": 4,
-        "type": "array"
-      },
-      "enabled": {
-        "type": "boolean"
-      },
-      "endSpeed": {
-        "exclusiveMinimum": 0,
-        "type": "number"
-      },
-      "startSpeed": {
-        "exclusiveMinimum": 0,
-        "type": "number"
-      }
-    },
-    "required": [
-      "enabled",
-      "startSpeed",
-      "endSpeed",
-      "curve"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "curve": {
+        "description": "Cubic bezier control points [c1x,c1y,c2x,c2y]",
+        "items": {
+          "type": "number"
+        },
+        "maxItems": 4,
+        "minItems": 4,
+        "type": "array"
+      },
+      "enabled": {
+        "type": "boolean"
+      },
+      "endSpeed": {
+        "exclusiveMinimum": 0,
+        "type": "number"
+      },
+      "startSpeed": {
+        "exclusiveMinimum": 0,
+        "type": "number"
+      }
+    },
+    "required": [
+      "enabled",
+      "startSpeed",
+      "endSpeed",
+      "curve"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

Changed1 schema field changedOct 8, 2026

changedInput schema / properties / speedRamp / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "curve": {
-        "description": "Cubic bezier control points [c1x,c1y,c2x,c2y]",
-        "items": {
-          "type": "number"
-        },
-        "maxItems": 4,
-        "minItems": 4,
-        "type": "array"
-      },
-      "enabled": {
-        "type": "boolean"
-      },
-      "endSpeed": {
-        "exclusiveMinimum": 0,
-        "type": "number"
-      },
-      "startSpeed": {
-        "exclusiveMinimum": 0,
-        "type": "number"
-      }
-    },
-    "required": [
-      "enabled",
-      "startSpeed",
-      "endSpeed",
-      "curve"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "curve": {
+        "items": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "number"
+          },
+          {
+            "type": "number"
+          },
+          {
+            "type": "number"
+          }
+        ],
+        "maxItems": 4,
+        "minItems": 4,
+        "type": "array"
+      },
+      "enabled": {
+        "type": "boolean"
+      },
+      "endSpeed": {
+        "exclusiveMinimum": 0,
+        "type": "number"
+      },
+      "startSpeed": {
+        "exclusiveMinimum": 0,
+        "type": "number"
+      }
+    },
+    "required": [
+      "enabled",
+      "startSpeed",
+      "endSpeed",
+      "curve"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

Changed1 schema field changedOct 7, 2026

changedInput schema / properties / speedRamp / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "curve": {
-        "items": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "number"
-          },
-          {
-            "type": "number"
-          },
-          {
-            "type": "number"
-          }
-        ],
-        "maxItems": 4,
-        "minItems": 4,
-        "type": "array"
-      },
-      "enabled": {
-        "type": "boolean"
-      },
-      "endSpeed": {
-        "exclusiveMinimum": 0,
-        "type": "number"
-      },
-      "startSpeed": {
-        "exclusiveMinimum": 0,
-        "type": "number"
-      }
-    },
-    "required": [
-      "enabled",
-      "startSpeed",
-      "endSpeed",
-      "curve"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "curve": {
+        "description": "Cubic bezier control points [c1x,c1y,c2x,c2y]",
+        "items": {
+          "type": "number"
+        },
+        "maxItems": 4,
+        "minItems": 4,
+        "type": "array"
+      },
+      "enabled": {
+        "type": "boolean"
+      },
+      "endSpeed": {
+        "exclusiveMinimum": 0,
+        "type": "number"
+      },
+      "startSpeed": {
+        "exclusiveMinimum": 0,
+        "type": "number"
+      }
+    },
+    "required": [
+      "enabled",
+      "startSpeed",
+      "endSpeed",
+      "curve"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

First observedOct 7, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It implies a mutation but never says whether this is a partial/merge update, whether omitted fields are preserved, that passing null on several fields removes styling, or that type changes require compatible fields. 'And more' actively obscures scope for a 50-parameter mutation 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?

Two short sentences, with the core action front-loaded. The trailing 'and more' is low-value filler but the overall footprint is tight and readable.

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?

For a 50-parameter mutation with nested objects, required ID relationships, and no annotations or output schema, the description is far too thin. It never explains partial-update behavior, the interplay of required IDs with legacy shorthand fields, or the risk profile of overwriting existing overlay configuration.

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 the schema already documents each of the 50 parameters thoroughly (including legacy shorthands, null-to-remove semantics, and enum values). The description's field list (text, position, timing, animation, opacity) adds no meaning beyond what the schema provides, so the 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?

States a specific verb+resource ('Update an existing overlay item') and enumerates a few mutable fields. However, it does not distinguish this from siblings like update_overlay_track, move_overlay_item_to_track, or delete_overlay_item, so the agent gets no help choosing among them.

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?

There is no when-to-use guidance, no prerequisites (e.g. that the item must already exist on the given track), and no mention of alternatives. The agent is left to infer everything about invocation context.

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

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

update_overlay_item

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources