Skip to main content
Glama
the-real-talk

the-real-talk

set_layout_grids

Applies grid, column, or row layout grids to a Figma frame, letting you define count, gutter, offset, section size, and alignment for precise responsive structure.

Instructions

Set the layout grids of a frame: GRID (square), COLUMNS or ROWS (count, gutterSize, offset, alignment, sectionSize).

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>",
      "grids": "<grids>"
    },
    "name": "set_layout_grids"
  }
}

Input Schema

NameRequiredDescriptionDefault
gridsYes
nodeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It signals a mutation by saying "Set" and names the grid properties, but never states that the grids array overwrites the frame's current grids, that at most 8 grids are allowed, or what happens on invalid node types. These are the behavioral facts an agent most needs before calling a destructive-feeling write.

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?

A single front-loaded sentence with no filler, and the pattern list is a compact way to convey the enum-like choices. It is dense but every clause carries information; the only cost is that the parenthetical field list reads like a schema echo rather than added meaning.

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

Completeness2/5

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

For a mutation tool with a nested array of up to 8 grid objects, no annotations, and no output schema, the description should cover replacement semantics and the full field set. It leaves out color, visible, nodeId, and the max-items limit, so an agent could easily construct an incomplete or unintended call.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must explain the parameters, and it only partially does: it lists count, gutterSize, offset, alignment, and sectionSize as grid fields but omits color and visible entirely, and says nothing about nodeId or the grids array itself. It also does not indicate which fields are meaningful for which pattern (e.g., sectionSize for COLUMNS/ROWS).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 ("Set the layout grids of a frame") and enumerates the three grid patterns, so an agent knows this writes grid definitions rather than layout mode, positioning, or sizing. It does not explicitly contrast itself with sibling tools like set_layout_mode or set_padding, but the resource is unambiguous enough to distinguish it in practice.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus alternatives (e.g., auto-layout settings vs. layout grids), no prerequisites such as the target node having to be a frame, and no note that existing grids are replaced. The agent must infer all of this.

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