Skip to main content
Glama
AE Motion MCP
by dha-aa

Get Keyframes

get_keyframes
Read-onlyIdempotent

Reads a property's keyframes—time, value, in/out interpolation, temporal ease, and active expression—or its value if unanimated, with offset/limit paging.

Instructions

Read the keyframes of one property: time, value, in/out interpolation and temporal ease, plus any active expression; unanimated, its value. Returns every key that fits; next_offset when there are more (offset continues; limit caps a page). Use list_properties to find the path.

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": {
      "layer_id": "<layer_id>",
      "path": "<path>"
    },
    "name": "get_keyframes"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
limitNo
offsetNo
layer_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.26.0
    • addedInput schema / properties / limit
      Added value: +{
      +  "type": "integer"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "type": "integer"
      +}
  2. First observedv2.22.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: 'Returns every key that fits' with a next_offset continuation token that 'offset continues', and that it returns a single value for unanimated properties. It does not state ordering, error behavior for bad paths, or whether expressions are evaluated or shown as source.

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?

Three dense sentences: return payload first, then paging behavior, then the prerequisite lookup. No filler, no repetition of the title, and the most load-bearing information is front-loaded.

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?

With no output schema, the description must convey return shape, and it does name the per-key fields plus the next_offset token and the unanimated fallback. Remaining gap is the path format (string vs segment array) and the layer_id/path relationship, which an agent must guess from the 0%-covered schema.

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 0%, so the description carries the burden, and it partially does: limit and offset are explained via the paging sentence, and path is contextualized by the list_properties pointer. However, layer_id is never mentioned, and the schema's polymorphic path (a string OR an array of string/number segments) is not explained at all, which is the subtlest part of the call signature.

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 opens with a specific verb and resource — "Read the keyframes of one property" — and enumerates the returned fields (time, value, in/out interpolation, temporal ease, active expression). It also defines the degenerate case (unanimated property returns its value), so an agent can distinguish it from the sibling write tools edit_keyframes and set_keyframes purely from the text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly routes path discovery to list_properties and gives concrete paging guidance ("next_offset when there are more", "limit caps a page"). What's absent is any explicit statement of when not to use it, e.g. that mutating keys requires set_keyframes/edit_keyframes rather than this read tool.

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