Skip to main content
Glama
Sign In

Montik

by app.montik
OverviewDiscussionsAdmin

Set animation

set_animation

Animate clips in and/or out (titles, captions, stickers, b-roll). Types: fade, pop, bounce, rise, slideLeft, slideRight, slideUp, slideDown, zoomIn, zoomOut, spinCw, spinCcw, typewriter (text only), wordRise (text only), wordPop (text only), wordFade (text only), wordReveal (text only), charRise (text only), charPop (text only), charFade (text only), lineRise (text only), lineReveal (text only). Out-animations mirror the motion (slideLeft out leaves to the left). Pass null to remove.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_animation"
  }
}

Input Schema

NameRequiredDescriptionDefault
inNo
outNo
clipIdNo
clipIdsNo
projectIdNoProject to act on (default: the open one)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already state readOnly=false and destructive=false, so the agent knows this is a non-destructive mutation. The description adds genuinely useful behavior not in the annotations: out-animations mirror the motion, and null removes the animation. It still doesn't say whether calling it replaces existing animations, what happens if both in and out are null, or how clipId and clipIds interact.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence and the null-removal note are front-loaded and earn their place, but the 24-item type list duplicates the schema enum verbatim, consuming most of the text for zero added information. Trimming that list would make the definition much tighter.

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 5-parameter mutation tool with no output schema, the description covers animation types and removal semantics but leaves the clip-targeting parameters (clipId vs clipIds) and the effect on pre-existing animations unexplained. It is adequate but not sufficient to invoke confidently on multi-clip or overwrite cases.

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 20%, so the description must carry the load, and it largely restates the enum the schema already lists. The undocumented, ambiguous parameters, clipId vs clipIds and the duration default, get no clarification; only the null-removal semantics and out-mirroring add meaning beyond 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?

The description opens with a specific verb and resource: "Animate clips in and/or out (titles, captions, stickers, b-roll)," which immediately tells the agent this applies in/out animations to clips. It does not name a sibling such as set_transition or add_effect to steer the agent away, so it stops short of full differentiation.

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

Usage Guidelines3/5

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

"Pass null to remove" gives one concrete usage rule, and the repeated "text only" tags guide type selection. However, there is no guidance on when to use this versus set_transition (between clips) or add_effect, nor on whether clipId or clipIds should be used when targeting multiple clips.

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

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