Skip to main content
Glama

Delete Keyframes

animation.delete_keyframes
Destructive

Remove keyframes from specified attributes of a node within a defined time range. Allows clearing animation data for selected attributes or all animated attributes.

Instructions

Delete keyframes in a time range for attribute(s).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeYesName of the node to delete keyframes from
attributesNoAttribute names (None = all animated attributes)
time_range_endNoEnd of time range (None = all time)
time_range_startNoStart of time range (None = all time)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeYes
errorsYes
attributesYes
time_rangeYes
deleted_countYes
Behavior3/5

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

Annotations already declare destructiveHint=true, and the description is consistent. However, it adds no new behavioral context beyond what is obvious (deletion). The description does not elaborate on irreversibility or side effects.

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 of six words with no superfluous content. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema and complete parameter documentation, the description covers the essential purpose. However, it could explicitly state that omitting time_range_start and time_range_end deletes all keyframes for the node.

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 fully documents all parameters. The description summarizes the parameters but adds no new meaning beyond what is in the schema.

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 clearly states the verb 'Delete', the resource 'keyframes', and the scope 'in a time range for attribute(s)'. It distinguishes itself from sibling tools like animation.get_keyframes and animation.set_keyframe by specifying deletion.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives, nor does it mention prerequisites or exclusions.

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/GimbalGoats/GG_MayaMCP'

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