Skip to main content
Glama
Sign In
Figxel

Figxel

by AvYour
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Set board properties (FigJam)

figma_set_board_properties
Idempotent

FigJam properties on 1–500 nodes, each applied by node type. color is a palette name resolved per type — sticky fill, shape preset (fill, stroke and text), connector line, table fill, text fill — or a hex; a section takes a hex only for…

Instructions

FigJam properties on 1–500 nodes, each applied by node type. color is a palette name resolved per type — sticky fill, shape preset (fill, stroke and text), connector line, table fill, text fill — or a hex; a section takes a hex only for now. wide, authorVisible (stickies), shape (shapes with text: a shape type), contentsHidden (sections), language (code blocks). A field that does not apply to a node's type is an error for that node, and that node is left unchanged. Hex paints on any node: figma_set_fills. Editors: unverified in FigJam, Slides.

Input Schema

NameRequiredDescriptionDefault
wideNoStickies: 416 wide instead of 240.
colorNoA palette name for each node's type, or a hex.
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.
shapeNoShapes with text: a shape type such as "diamond".
nodeIdsYes
sessionNoOptional sessionId or file name, to pick a Figma file when more than one is connected.
languageNoCode blocks: typescript, javascript, python, go, rust, ruby, css, html, json, graphql, sql, swift, kotlin, cpp, bash, plaintext, dart.
authorVisibleNoStickies: show the author.
contentsHiddenNoSections: hide what they hold.
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.1/5.0
Behavior4/5

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

Annotations already cover the write, idempotent, and non-destructive profile. The description adds useful behavioral detail: fields are validated per node type, inapplicable fields cause an error for that node, and that node is left unchanged. It still omits some mutation behavior such as stale-write handling, though the force parameter documents that in the schema.

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 dense but efficient, front-loads the FigJam/node-type scope, and avoids repeating the schema mechanically. The final note about editors is somewhat cryptic, but the paragraph otherwise earns its space.

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 10-parameter FigJam mutation tool with no output schema, the description gives enough context to call it correctly: node scope, type-specific fields, color semantics, and partial-failure behavior. Remaining gaps like force/idempotency/session details are covered adequately by the schema.

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 high at 90%, so the schema carries most parameter documentation. The description still adds valuable semantics by explaining how color resolves per node type, how sections differ, and which fields apply to stickies, shapes, sections, and code blocks.

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 clearly identifies the resource and operation: FigJam board properties applied to 1–500 nodes by node type. It also distinguishes hex paint changes from this tool by explicitly routing them to figma_set_fills.

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

Usage Guidelines3/5

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

The FigJam and per-node-type scope implies when the tool is appropriate, and the description names figma_set_fills as the alternative for hex paints. However, it does not explicitly compare against sibling property-setting tools such as figma_set_text_properties or figma_set_slide_properties.

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