Skip to main content
Glama

GSAP Tween Generator

gsap_tween

Create GSAP tweens for single-target animations with methods: to, from, fromTo, set. Define properties, easing, stagger, and callbacks.

Instructions

Generate a single GSAP tween (gsap.to, gsap.from, gsap.fromTo, gsap.set). Use for one-off animations on a single target. For sequenced multi-step animations use gsap_timeline instead. For common patterns like fadeIn or slideUp use gsap_preset instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
easeNoEasing function name, e.g. 'power2.out', 'elastic.inOut', 'back.out(1.7)'. Use gsap_easing tool to browse available easings.power1.out
yoyoNo
delayNo
methodYes'to' animates TO the given values (most common). 'from' animates FROM the given values to current state. 'fromTo' animates between two explicit states. 'set' applies values instantly with no animation.
repeatNo
targetYesCSS selector or target description
staggerNo
durationNo
overwriteNo
onCompleteNoFunction name to call on complete
propertiesYesGSAP animation properties. Use transform shorthands (x, y, scale, rotation) not CSS transform. Use autoAlpha instead of opacity+visibility. Values can be numbers, strings ('+=100', '50%'), or arrays for keyframes.
fromPropertiesNoStarting properties — required for fromTo method
includeImportsNoSet to false when generating a snippet to insert into existing code that already has GSAP imported.
Behavior3/5

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

No annotations provided, so description carries full burden. It states the tool generates a tween but does not specify output format (e.g., returns code?, applies to DOM?). Lacks detail on side effects or exact behavior beyond the methods listed. Adequate but not rich.

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?

Two sentences, no fluff. Gets straight to purpose and usage guidance. Highly concise.

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

Completeness2/5

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

Given 13 parameters, nested objects, and no output schema, the description is too minimal. It does not explain what the tool produces (e.g., a code snippet, a function call, logs to console?) or how the result is delivered. Incomplete for such a complex tool.

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 coverage is 54% (low), but description does not add any parameter meanings beyond what's already in the schema. The description is separate and does not compensate for undocumented parameters. Falls short of adding value.

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?

Description clearly states 'generate a single GSAP tween' and lists the specific methods (gsap.to, from, fromTo, set). It distinguishes from sibling tools like gsap_timeline and gsap_preset by explicitly noting they are for sequenced or common patterns.

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?

Explicitly states when to use this tool ('one-off animations on a single target') and when not to ('sequenced multi-step animations' - use gsap_timeline; 'common patterns like fadeIn' - use gsap_preset). Provides clear alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bl00dclot/gsap-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server