Skip to main content
Glama
Sign In
mcp-ae

mcp-ae

by shibin0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ae_set_layer_time

Set the in point, out point, or start time of any layer in an After Effects composition. Provide composition and layer names, then specify timing in seconds to control precisely when the layer starts or stops.

Instructions

Set the in point, out point, or start time of a layer

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": {
      "comp_name": "<comp_name>",
      "layer_name": "<layer_name>"
    },
    "name": "ae_set_layer_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
in_pointNoIn point in seconds
comp_nameYesComposition name
out_pointNoOut point in seconds
layer_nameYesLayer name
start_timeNoStart time in seconds (shifts the layer in time)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It states that the tool sets timing attributes but does not disclose side effects, whether setting multiple values interacts, whether in/out points trim the layer, or whether changes are reversible. This is minimal behavioral context.

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?

The description is a single, front-loaded sentence with no filler. It communicates the tool's core function immediately and every word adds signal.

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 tool with no annotations, no output schema, and five parameters, this description is too thin. It does not explain parameter interactions, expected effects on the layer's timeline, prerequisites, or what happens when optional values are omitted. An agent would need to look elsewhere to safely invoke it 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?

Schema description coverage is 100%, so the schema already explains each parameter such as in_point being 'In point in seconds' and start_time 'shifts the layer in time'. The description only echoes the parameter names and adds no meaning beyond the schema, so the baseline of 3 is appropriate.

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?

The description names an exact verb ('Set'), a resource ('layer'), and the specific attributes affected ('in point, out point, or start time'). This clearly distinguishes it from generic sibling tools like ae_set_layer_property and from timing-related tools like ae_add_keyframe or ae_enable_time_remap.

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 gives no explicit guidance on when to use this tool versus alternatives, and it does not mention prerequisites such as the layer needing to exist or the composition being currently open. Usage must be inferred entirely from the tool name and the one-line action statement.

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