Skip to main content
Glama
Lillard01
by Lillard01

create_timeline_animation

Create complex timeline animation sequences by defining targets, properties, durations, and positions for chained animations.

Instructions

创建复杂的时间轴动画序列

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
optionsNo时间轴选项
animationsYes
timelineIdNo时间轴唯一标识符
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the creation action, with no information about side effects, required permissions, or whether it modifies existing state. The description is insufficient for safe usage.

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

Conciseness2/5

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

The description is a single short sentence, which is too brief for a tool with three parameters and nested objects. It lacks structure, front-loading of key information, any additional helpful context.

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 the tool's complexity (nested array input, multiple sibling tools, no output schema, no annotations), the description is far from complete. It fails to explain what constitutes a 'complex' animation, how to use the animantions parameter, or what the result is.

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 67%, with two parameters having descriptions. However, the tool description adds no additional meaning or context for the parameters, such as how the 'animations' array component is structured or what 'options' and 'timelineId' accept. It does not compensate for the missing 33% coverage.

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 clearly states the action '创建复杂的时间轴动画序列' (create complex timeline animation sequences) with a specific verb and resource. However, it does not differentiate this tool from sibling timeline or animation tools, such as 'create_sync_timeline' or 'create_stagger_animation'.

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?

The description provides no guidance on when to use this tool versus the many sibling tools. There is no mention of prerequisites, context, or when not to use it.

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/Lillard01/GSAP-mcp'

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