Skip to main content
Glama
Lillard01
by Lillard01

timeline_scrubber

Control a GSAP timeline's progress interactively by adding a draggable scrubber to a specified container, with optional labels and progress display.

Instructions

时间轴拖拽控制

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
showLabelsNo显示标签
timelineIdYes时间轴ID
showProgressNo显示进度
scrubberContainerYes控制器容器选择器
Behavior2/5

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

No annotations exist, so the description must disclose behavioral traits. It merely states 'timeline drag control' with no information about side effects, permissions, or what happens to the timeline. Essential details like whether it modifies state or just returns UI are missing.

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 extremely short (4 words) but under-specified for a tool with 4 parameters. It sacrifices necessary detail for brevity, making it insufficient.

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?

The tool has no output schema and no annotations, yet the description provides no context about return values, behavior, or how it integrates with other animation tools. Incomplete for an AI agent to select and invoke correctly.

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

Parameters3/5

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

The input schema covers all 4 parameters with descriptions, so baseline is 3. The tool description adds no extra meaning beyond the schema. The schema descriptions are clear but minimal.

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 description 'timeline drag control' indicates a verb+resource but is vague. It doesn't specify whether it initializes, enables, or configures a scrubber, and it fails to distinguish from sibling tools like 'create_timeline_animation' which also involve timelines.

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?

No guidance is provided on when to use this tool versus the many animation sibling tools. There is no mention of prerequisites, exclusions, or context.

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