Skip to main content
Glama
Figma Local Bridge

Figma Local Bridge

by Miart

figma_motion_remove_keyframes

Remove a node field's manual keyframe track in Figma Motion Beta with a dry-run preview by default. Apply mode verifies the track is gone and rolls back if removal fails.

Instructions

Remove the manual keyframe track on one field of a node (Motion Beta). dryRun defaults to TRUE and reports the current track. Removing an absent track is a verified no-op. Apply verifies the field no longer has a manual track and rolls back otherwise.

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": {
      "field": "<field>"
    },
    "name": "figma_motion_remove_keyframes"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldYes
dryRunNoTRUE (default): plan only, no document write. FALSE: apply in one undo transaction.
nodeIdNoDefaults to the current single selection
planIdNoThe planId returned by the dry run. Apply is refused if the arguments or the node's Motion state changed.
fileKeyNoWhich connected Figma file to use: its fileKey (figma_whoami) or, when omitted, the only connected file. Required once more than one file is connected; figma_ping lists them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.36.0

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full disclosure burden and does so well: absent-track removal is a verified no-op, apply is verified and rolled back on failure, changes happen in one undo transaction, and a stale planId blocks the write. These are exactly the safety and side-effect facts an agent needs before mutating a document.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with purpose, then the dry-run/apply mechanic and the no-op/rollback guarantees. Every sentence contributes. A slightly tighter phrasing of the dryRun sentence could shave a clause, but there is no filler.

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?

No output schema exists, so the description must hint at returns: it says the dry run 'reports the current track' but not what that plan payload contains or how it maps to planId. For a mutation with a nested field selector and 5 parameters, the dry-run/apply/rollback cycle plus verification are otherwise adequately covered.

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 80%, so field, index, collection, propertyId, and fileKey already document themselves thoroughly. The description restates dryRun's default/behavior and implies planId's invalidation semantics, which the schema also covers. It adds little parameter meaning beyond the structured data, so the baseline 3 applies.

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 states a specific verb and resource: 'Remove the manual keyframe track on one field of a node', and scopes it to a single field rather than a whole node or style. That distinguishes it cleanly from figma_motion_set_keyframes (sets tracks) and figma_motion_remove_style (removes a style), so an agent can pick it without opening a schema.

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 conveys a concrete usage pattern: dryRun defaults to TRUE and only plans, whereas FALSE applies; apply is refused if arguments or the node's Motion state changed since the dry run. That is clear operational guidance. It does not explicitly name when to prefer a sibling such as figma_motion_set_keyframes or figma_motion_remove_style, so a small gap remains.

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