Skip to main content
Glama

Morpha

by ai.morphareels
OverviewDiscussionsAdmin

Add keyframes

add_keyframes
Destructive

Add many keyframes to ONE element's ONE property in a single call, with an optional loop mode applied in the same call. The idiomatic form when every layer in a multi-element animation gets its own track (ripple dot pulse, snowflake fall, equaliser-bar wave). Factors elementId + property out of the loop body and folds set_track_loop in. Use set_keyframes_batch instead when you need to mix elements/properties in one atomic call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
loopNoOptional extrapolation mode applied to this track in the same call. Default 'hold'.
propertyYes
elementIdYesLayer id (video.<id>, image.<id>, shapes.<id>, text.<id>, or group.<id>).
keyframesYesKeyframes for this track (one or more).
projectIdYesOpaque project id (a v4 UUID, from list_projects/create_project). Selects which existing project this call mutates.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the call succeeded.
dataNoThe payload, shaped by the tool.
noteNoWhat to do next when not ready.
errorNoWhy it failed.
statusNoFor cache-backed readers: whether the answer was ready.
editorUrlNoOpens this project in the editor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / anonymousToken
      Removed value: -{
-  "description": "The token create_anonymous_account returned. This connection has no Morpha key, so every call carries it.",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "elementId",
-  "property",
-  "keyframes",
-  "projectId",
-  "anonymousToken"
-]New value: +[
+  "elementId",
+  "property",
+  "keyframes",
+  "projectId"
+]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "The result envelope every Morpha tool returns.",
+  "properties": {
+    "data": {
+      "description": "The payload, shaped by the tool.",
+      "type": [
+        "object",
+        "array",
+        "string",
+        "number",
+        "boolean",
+        "null"
+      ]
+    },
+    "editorUrl": {
+      "description": "Opens this project in the editor.",
+      "type": "string"
+    },
+    "error": {
+      "description": "Why it failed.",
+      "type": "string"
+    },
+    "note": {
+      "description": "What to do next when not ready.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the call succeeded.",
+      "type": "boolean"
+    },
+    "status": {
+      "description": "For cache-backed readers: whether the answer was ready.",
+      "enum": [
+        "ready",
+        "not-ready"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}
  3. Changed2 schema fields changed
    • addedInput schema / properties / anonymousToken
      Added value: +{
+  "description": "The token create_anonymous_account returned. This connection has no Morpha key, so every call carries it.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "elementId",
-  "property",
-  "keyframes",
-  "projectId"
-]New value: +[
+  "elementId",
+  "property",
+  "keyframes",
+  "projectId",
+  "anonymousToken"
+]
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already flag mutating/destructive behavior, and the description adds useful side-effect context: it can fold set_track_loop into the same call and factors elementId/property out of the caller's loop. It does not spell out whether existing keyframes are replaced or appended, but that is not required once destructiveHint and output schema are present.

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 sentences with distinct jobs: purpose, use case, alternative. The purpose and key constraint are front-loaded, and the examples are compact and illustrative rather than filler.

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

Completeness5/5

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

For a 5-parameter mutation tool, the description plus rich schema, annotations, and output schema cover what the tool does, when to use it, and how it differs from the closest sibling. No critical calling decision is left unaddressed.

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 high (80%) and already documents elementId, keyframes, projectId, and loop with enums/defaults. The description adds contextual meaning for elementId/property factoring and loop-mode folding, but it does not materially explain parameter formats beyond the schema, so the high-coverage baseline of 3 is appropriate.

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 opens with a specific verb-plus-resource statement: 'Add many keyframes to ONE element's ONE property in a single call,' then narrows scope (per-layer tracks) and explicitly contrasts with set_keyframes_batch. This makes the tool unambiguous among the many add_* and keyframe siblings.

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

Usage Guidelines5/5

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

It states the intended scenario ('idiomatic form when every layer in a multi-element animation gets its own track') and gives explicit alternative routing ('Use set_keyframes_batch instead when you need to mix elements/properties in one atomic call'). This is exactly the when/when-not guidance an agent needs.

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

All Morpha 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