Remove a keyframe from an After Effects layer property by specifying its 1-based index. Directly deletes the selected keyframe to clean up animation.
Delete a specific keyframe from a layer property by index (1-based)
| Name | Required | Description | Default |
|---|---|---|---|
| comp_name | Yes | Composition name | |
| layer_name | Yes | Layer name | |
| property_path | Yes | Property path | |
| keyframe_index | Yes | 1-based keyframe index to delete |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It makes the destructive nature and the 1-based indexing explicit, but it does not mention that deleting a keyframe shifts subsequent keyframe indices or what happens if the index is out of range.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence with no filler. Every word contributes to understanding the tool's core behavior.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is minimally viable for a simple delete operation, and the schema covers all required parameters. However, since there are no annotations and no output schema, the description could usefully add edge-case behavior or note that deleting by index may invalidate previously-known keyframe indices.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already documents all four parameters with 100% coverage, so the description does not need to repeat them. It adds a small amount of meaning by clarifying the keyframe index is 1-based, but it does not explain property_path syntax or other parameter nuances.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Delete'), a precise resource ('a specific keyframe from a layer property'), and the selection mechanism ('by index (1-based)'). This clearly distinguishes it from related sibling tools like ae_add_keyframe or ae_get_keyframes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The intended use is clear: remove a particular keyframe identified by its index. It does not explicitly discuss when not to use it or recommend alternatives, but the one-sentence context is enough to route an agent correctly among keyframe-related tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.