Skip to main content
Glama
Sign In
OpenCode Figma MCP

OpenCode Figma MCP

by yhoyoex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_scroll_behavior

Set frame overflow direction and child scroll behavior to control scrolling in Figma prototypes, making elements fixed or scrollable.

Instructions

Set prototype scrolling: overflowDirection on a frame, and/or make a child FIXED (fix position when scrolling) or SCROLLS. FIXED moves the node to the top of its parent's layer order (last child); in an auto-layout parent this also changes the node's position in the flow. SCROLLS moves a fixed node back to the top of the scrolling children. STICKY_SCROLLS is not supported by the Figma Plugin API and returns an error.

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": {
      "nodeId": "<nodeId>"
    },
    "name": "set_scroll_behavior"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYesID of the node (a frame for overflowDirection, a child of a frame for scrollBehavior)
scrollBehaviorNoScroll behavior of the node inside its parent frame
overflowDirectionNoScroll direction of the frame's overflowing content

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose key side effects the schema omits: FIXED reorders the node to last child (with flow implications in auto-layout) and SCROLLS moves a fixed node back. It stops short of covering permissions, reversibility, or what a failed call returns beyond the STICKY_SCROLLS error.

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?

Front-loaded with the core purpose, then dense side-effect detail in following sentences. Every sentence carries information, though the FIXED/SCROLLS mechanics make it somewhat dense relative to a 3-parameter tool.

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?

Complete enough for a mutation tool with no annotations and no output schema: it covers both parameter roles, the main enum behaviors, and the unsupported-value error. It leaves minor edge cases (e.g. node outside a frame, prototype-mode requirements) unstated.

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 adds real meaning beyond the schema by explaining the side effects of the FIXED, SCROLLS, and STICKY_SCROLLS enum values that the terse schema descriptions do not convey.

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?

States a specific verb (Set) and resource (prototype scrolling) and separates the two distinct operations: overflowDirection on a frame and scrollBehavior on a child. An agent can immediately tell what the tool manipulates and how the two parameters differ.

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?

Gives clear conditions for using each parameter (overflowDirection on a frame, scrollBehavior on a child) and flags that STICKY_SCROLLS is unsupported and errors. It does not name any sibling tool as an alternative or state when not to use this tool, but the context of use is unambiguous.

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

Deploy Server

Other Tools