Montik

Add html overlay

add_html_overlay

Put an animated HTML overlay on the timeline: a library component with props (see list_components), or your own html/css/js. HTML overlays are full-frame transparent pages (project width x height px) laid over the video for the clip's duration. Authoring rules (the exporter seeks the page frame by frame, so motion must be seekable):

Animate with CSS @keyframes / transitions or the Web Animations API. Time 0 = clip start. Do not use setTimeout/requestAnimationFrame for motion.
For JS-driven motion define window.montikSeek = (t, duration) => {...} (e.g. gsapTimeline.seek(t)).
Exit animations: animation-delay: calc(var(--clip-duration) - 0.4s) with fill-mode forwards.
Your project's images: {{media:ID}} (ids from list_media) becomes the image's address, in html, css, js or a prop: . PNG, JPEG, WebP and GIF. A page can show one but can't read its pixels back from a canvas.
Brand variables: --brand-primary --brand-secondary --brand-accent --brand-text --brand-background, --font-heading --font-body, --brand-logo (url). Use them instead of hard-coded colours/fonts.
Lay out in px against the frame (var(--frame-w) / var(--frame-h)); keep text inside safe areas (avoid the top 8% and bottom 15% on vertical video).
No external network requests except fonts already in the library. Emoji render natively.
Design: one message per graphic, set as type in the shot's empty space, in the brand fonts. No eyebrow/kicker labels, pills, emoji, gradient text or white drop-shadow cards unless the brand calls for them; one motion idea per ad, easing out. See the brand-overlays playbook. Check the result with render_frame.

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": {
      "start": "<start>"
    },
    "name": "add_html_overlay"
  }
}

Input Schema

Name	Required	Description
`js`	No
`css`	No
`html`	No
`name`	No
`props`	No
`start`	Yes
`trackId`	No	a text/graphics track; default picks or creates one
`duration`	No
`component`	No
`projectId`	No	Project to act on (default: the open one)
`transform`	No	x/y: offset in project pixels from canvas center (+y is down). scale: 1 = fit. rotation: degrees

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false. The description adds crucial execution behavior beyond that: the exporter seeks frame by frame, motion must be CSS/WAAPI or window.montikSeek, setTimeout/requestAnimationFrame are disallowed, external network requests are restricted, and overlays are full-frame transparent pages with safe-area constraints.

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?

The core action is front-loaded, and the long authoring guidance is organized into bullets. Most sentences earn their place by preventing invalid overlays, though the design-preference prose about eyebrow labels, pills, and motion ideas is prescriptive rather than essential to tool selection.

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?

The description covers the complex authoring and rendering model well, but for an 11-parameter add tool with no output schema it omits timing/placement parameter meanings and does not explain what the tool returns, such as an overlay id needed for update_html_overlay.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 27% across 11 parameters. The description explains html/css/js, component, props, media placeholders, and brand variables, but says nothing about the required start parameter's units or semantics, duration, name, or transform, leaving most timing and placement parameters undocumented.

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?

States a specific verb and resource: 'Put an animated HTML overlay on the timeline.' It also distinguishes the two supported modes, a library component via list_components or your own html/css/js, which separates it from add_text, add_clip, and update_html_overlay.

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?

Gives clear usage context: choose a library component or custom markup, consult list_components, use {{media:ID}} from list_media, and verify with render_frame. It does not explicitly state when to prefer add_text or add_clip over this tool, so it stops short of full when/when-not routing guidance.

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

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

Resources

Need Help?