Skip to main content
Glama
Figma Local Bridge

Figma Local Bridge

by Miart

figma_motion_remove_style

Remove one applied Motion Beta animation style from a Figma node by its applied instance ID, with dry-run planning by default and verified apply with rollback.

Instructions

Remove one applied animation style by its applied instance id (not the style definition id) from a node (Motion Beta). dryRun defaults to TRUE. Removing a style that is not present is a verified no-op, not an error. Apply verifies the id is gone after the write 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": {
      "appliedStyleId": "<appliedStyleId>"
    },
    "name": "figma_motion_remove_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
appliedStyleIdYesThe applied style's `id` from figma_motion_inspect

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.36.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does well: it declares the safe default (dryRun TRUE), the no-op semantics for missing styles, post-write verification, rollback on failure, and the Motion Beta status. It doesn't cover permissions or what the apply response contains, but the mutation-safety profile is unusually well specified.

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 the core action and id disambiguation, then behavior. Every sentence carries information; the only minor cost is that the dry-run/apply relationship is compressed into terse clauses rather than laid out as an explicit sequence.

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

Completeness3/5

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

For a 5-parameter mutation tool with no annotations and no output schema, the description covers the risky behavior well but never says what the dry run returns (the planId the caller must feed back) or what apply returns on success. The important safety facts are present, though the round-trip contract is left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description genuinely adds meaning by warning which id field to use and by linking the apply step to the previously returned planId/workflow. That is real disambiguation beyond the schema's own wording.

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 a specific verb and resource (remove one applied animation style from a node) and explicitly disambiguates the id type: the applied instance id, not the style definition id. That distinction alone lets an agent tell it apart from definition-level tools like figma_motion_styles or figma_motion_apply_style.

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 establishes the dry-run-first workflow (dryRun defaults to TRUE) and clarifies that removing an absent style is a no-op rather than an error, which is exactly the guidance an agent needs before retrying or erroring. It stops short of naming a sibling alternative or stating explicit exclusions, so it is clear context without full routing.

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