Skip to main content
Glama
Figma Local Bridge

Figma Local Bridge

by Miart

figma_motion_set_duration

Set a Figma Motion timeline's duration in seconds using its timeline id. Dry-run first, then apply with rollback if Figma reports a different duration.

Instructions

Set a Motion timeline's duration in seconds (Motion Beta). Pass the timeline id from figma_motion_inspect; the node must list that timeline. dryRun defaults to TRUE. Apply reads the timeline back and rolls back if Figma reports a different duration or the timeline disappears.

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": {
      "timelineId": "<timelineId>",
      "duration": "<duration>"
    },
    "name": "figma_motion_set_duration"
  }
}

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.
durationYesSeconds
timelineIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.36.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses that dryRun defaults to TRUE, that apply verifies by reading the timeline back, and that it rolls back if the duration differs or the timeline vanishes. It omits permission/auth requirements and failure modes for the dry run itself, so it is not exhaustive.

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 short sentences, front-loaded with the action, then prerequisites, then the dry-run/rollback contract. Every sentence adds information an agent needs; 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?

For a six-parameter mutation tool with no output schema and no annotations, the definition covers the critical behavior: default dry run, verification, and rollback semantics. It leaves out what a dry run returns and permission requirements, which are minor gaps given the otherwise strong disclosure.

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 already 83%, so the baseline is 3. The description still adds meaning: duration is in seconds, timelineId must originate from figma_motion_inspect, and the node must list that timeline, which clarifies nodeId/timelineId relationships beyond the schema text.

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 ('Set a Motion timeline's duration in seconds') and scopes it to Motion Beta, which cleanly separates it from siblings such as figma_motion_set_keyframes and figma_motion_apply_style. An agent can identify the operation without opening the 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 gives concrete preconditions: the timelineId must come from figma_motion_inspect and the node must list that timeline. It also explains the dry-run-first workflow. It does not name an explicit alternative tool or a when-not condition, so it falls short of a 5.

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