Skip to main content
Glama

animate_product_interface

Apply push, pan, reveal, or hold choreography to a selected timeline shot to create controlled product-interface motion for promotional video scenes.

Instructions

Set implemented push, pan, reveal or hold choreography on a real timeline shot.

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": {
      "timeline": "<timeline>",
      "shotIndex": "<shotIndex>",
      "output": "<output>"
    },
    "name": "animate_product_interface"
  }
}

Input Schema

NameRequiredDescriptionDefault
motionNopush
outputYes
timelineYes
shotIndexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is clear without the description. The description adds almost nothing beyond that: it does not say whether existing choreography on the shot is replaced, what 'implemented' implies about a prior step, or whether re-running changes the result.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the terseness leaves the surrounding gaps unfilled rather than being a model of density.

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

Completeness4/5

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

Placed correctly: an output schema exists, so return values need not be described, and annotations carry the mutation/safety profile. What remains missing is the zero-coverage parameter documentation and the differentiation from the sibling creation tools, so a 4 rather than a 5.

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 0% across four parameters, so the description must compensate and it only does so for one: the four motion values (push, pan, reveal, hold) are listed but the default 'push' is not. It says nothing about what 'timeline' accepts (ID? name?), what shotIndex 0-29 indexes into, or what 'output' is.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Set' and the resource ('choreography on a real timeline shot') plus the four named motion modes give a rough idea, but 'implemented ... choreography' is jargon-heavy and the tool is not distinguished from neighbours like create_camera_movement, create_motion_scene or create_transition. An agent can guess it applies motion to an existing shot, but must infer it.

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 prerequisite (e.g. shot must already exist in the timeline), and no indication of how this differs from the create_* motion or transition tools. The only implicit hint is 'timeline shot', which suggests an existing shot rather than a new scene.

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