Skip to main content
Glama

ae_setCurrentTime

Moves the After Effects playhead to a specified time in a composition, letting you jump to any frame programmatically. Omit the comp name to target the active composition.

Instructions

After Effects: move the comp playhead (current time indicator).

Input Schema

NameRequiredDescriptionDefault
timeYes
compositionNameNoComp name; omit to use the active comp.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so safety is covered. Beyond that the description adds nothing behavioral: it does not say what 'time' units are (seconds vs. frames), whether the playhead move affects keyframes/rendering, or what happens if the supplied comp is not open.

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?

A single short sentence with zero waste and the resource front-loaded, but its brevity comes at the cost of needed detail rather than being efficiently informative.

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?

For a two-parameter mutation tool with no output schema and half its schema undocumented, the description should at minimum specify time units and whether the target comp must be open. Neither is present, leaving an agent unable to call it confidently.

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 only 50%: compositionName is documented, but the critical 'time' parameter has no description and neither does the tool description clarify its units or accepted range. The description fails to compensate for the coverage gap on the one required parameter.

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?

Names a specific verb ('move') and resource ('comp playhead / current time indicator'), which is clear and distinguishable from the Premiere sibling pr_setPlayhead. No explicit sibling differentiation, but the AE prefix and playhead wording make scope obvious.

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 statement of when to use this versus alternatives such as ae_setKeyframe or ae_timeRemap, and no prerequisites (e.g., an open comp) are given. Usage is only implied by the tool name.

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

Deploy Server

Other Tools