Skip to main content
Glama
Sign In
Figxel

Figxel

by AvYour
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create section

figma_create_section
Idempotent

A section — the container designers use to organise a page by flow, and on a FigJam board the structure itself: a white wrapper, zones inside it, cards inside those (parentId = another section).

Instructions

A section — the container designers use to organise a page by flow, and on a FigJam board the structure itself: a white wrapper, zones inside it, cards inside those (parentId = another section). name: "" leaves it untitled when a title text inside carries the label. To fill a section and fit it to its content in one call, use figma_create_from_spec with a section's arrange and hug. Editors: Design; unverified: FigJam, Slides.

Input Schema

NameRequiredDescriptionDefault
xNoIn the parent's coordinates.
yNo
fillNoBackground colour, e.g. #F5FBFF.
nameNoShort and navigational, e.g. "Brainstorm"; "" for none.
forceNoOverwrite on purpose. A write to a node someone changed after you last read it is refused (STALE); read it again and resend instead. Pass true only when the person said to overwrite their edit.
widthNoDefault 800.
heightNoDefault 600.
sessionNoOptional sessionId or file name, to pick a Figma file when more than one is connected.
parentIdNoA page or a section. Defaults to the current page.
contentsHiddenNoHide what is inside, as FigJam's Hide contents. Default false.
idempotencyKeyNoCaller-owned retry key, ≤128 chars. Re-calling with the same key never executes twice: it returns the existing result, or waits for the op still in flight. Supply your own for anything large — if the MCP client times out (rather than the bridge), only a key you chose can be used to retry safely.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • addedInput schema / properties / force
      Added value: +{
+  "description": "Overwrite on purpose. A write to a node someone changed after you last read it is refused (STALE); read it again and resend instead. Pass true only when the person said to overwrite their edit.",
+  "type": "boolean"
+}
  2. First observedv0.1.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, destructive, idempotent, and open-world behavior, and the description does not contradict them. It adds useful editor-support context ('Design; unverified: FigJam, Slides') and describes FigJam structural behavior, though it does not discuss return values or failure modes beyond what the schema already covers.

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?

The description is fairly compact and front-loads the section concept and nesting model. The first sentence is dense, but each part contributes to understanding the tool's domain and the key alternative.

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?

Given 11 parameters, no required fields, 91% schema coverage, and strong annotations, the description provides enough context to select and call the tool. A minor gap is that with no output schema, it does not say what a successful creation returns, but the essential creation and nesting semantics are present.

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 description coverage is 91%, so the baseline is 3, but the description adds meaning for `name` by explaining when an empty name pairs with a title text, and for `parentId` by noting it can be another section. It does not add much beyond the schema for the other parameters.

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 clearly identifies the resource as a section and explains its role as a page-organising container, including FigJam nesting. It distinguishes the tool from `figma_create_from_spec` for the fill-and-fit case, though the description itself does not explicitly say 'creates' and relies on the title/name for the verb.

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 a concrete alternative: to fill and fit a section in one call, use `figma_create_from_spec` with `arrange` and `hug`. It also explains the `name: ""` untitled case and that `parentId` can be another section, but it does not broadly compare when to use a section versus a frame or page.

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