Skip to main content
Glama

fx_create

Create or update custom Remotion animated effects in TSX when built-in components fall short. Returns a preview image so you can review the effect before using it as an overlay.

Instructions

Create or update a custom animated effect when the built-in components can't do what the user wants. Write a React component (TSX) for Remotion:

  • Only import from "react" and "remotion" (useCurrentFrame, useVideoConfig, interpolate, spring, Easing, AbsoluteFill, Sequence…). No network, no require.

  • export default function Fx(props) {...}; draw on a TRANSPARENT background; size everything relative to useVideoConfig().width/height.

  • props.brand has colors {text, highlight, emphasis, outline, box}; font families 'VS Heading', 'VS Body', 'VS Deva', 'VS Guru' are loaded. Returns a 4-frame preview image (or the build/render error to fix). Show the preview to the user before using it as overlay component "fx:".

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": {
      "name": "<name>",
      "description": "<description>",
      "code": "<code>"
    },
    "name": "fx_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
nameYes
previewNo
brandKitNo
descriptionYes
defaultPropsNo
backgroundAssetNoShow the preview over a frame of the user's video
defaultDurationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the behavioral burden and does well: it defines the return value (a 4-frame preview image or the build/render error to fix), the sandbox constraints (only react/remotion imports, no network, no require), and rendering requirements (transparent background, sizing relative to useVideoConfig()). It leaves open what happens on a name collision with an existing effect and whether validation/rendering is expensive or slow.

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?

Purpose and trigger are front-loaded in the first sentence, followed by tight bullets covering imports, export shape, background, and sizing, then the return value and required user-confirmation step. Dense but every line encodes a real constraint; only minor tightening is possible.

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

Completeness3/5

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

For a code-authoring tool with eight parameters, nested `preview`/`backgroundAsset` objects, and no output schema, the description is solid on the component contract and the preview return but thin on the preview configuration and default-props surface. An agent could write the code correctly yet be unsure how to populate `preview`, `defaultDuration`, or `brandKit`.

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 only 13%, so the description must compensate, and it only partly does. It richly documents the required `code` content and implies the `name` pattern via the "fx:<name>" reference, plus explains `props.brand` colors and loaded fonts, but says nothing about `preview` (aspect/duration/props), `defaultProps`, `defaultDuration`, or `brandKit` — four of the eight parameters remain semantically opaque.

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 pair (create or update) and a precise resource (a custom animated effect authored as a Remotion TSX component), and scopes it to the case 'when the built-in components can't do what the user wants.' No sibling tool in the list deals in Fx components, so the agent can route correctly from the description alone.

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 states the trigger condition (built-in components insufficient) and prescribes a concrete post-call workflow: show the 4-frame preview to the user before referencing the effect as overlay component "fx:<name>". It does not state when not to use it, e.g. whether simpler styling should go through a style-save path instead, so it falls short of full when/when-not/alternatives coverage.

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