Skip to main content
Glama
KaiUweHella

figma-bridge-mcp

by KaiUweHella
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

figma_render

Render JSX or a batch of roots into Figma to convert code into design elements.

Instructions

Render one JSX value or roots[] batch into Figma.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNo
yNo
gapNo
jsxNo
iconsNo
labelNoOptional intent stored only as non-reversible audit metadata.
rootsNo
presetNo
verifyNo
confirmNoRequired by policy; omission is not a preview.
fileKeyNoFigma key/URL.
previewNoReturn a payload-free, non-mutating Command Plan.
manifestNo
directionNo
collectionNo
asComponentNo
keepWrapperNo
resizeProbeNo
smartPositionNo
allowedFreePathsNo
approvedFallbacksNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed22 schema fields changedv0.6.1
    • addedInput schema / properties / allowedFreePaths
      Added value: +{
+  "items": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 100,
+  "type": "array"
+}
    • addedInput schema / properties / approvedFallbacks
      Added value: +{
+  "items": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 100,
+  "type": "array"
+}
    • addedInput schema / properties / asComponent
      Added value: +{
+  "type": "boolean"
+}
    • addedInput schema / properties / collection
      Added value: +{
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / properties / confirm / description
      Previous value: -"Required when write-confirm mode is on."New value: +"Required by policy; omission is not a preview."
    • addedInput schema / properties / direction
      Added value: +{
+  "enum": [
+    "row",
+    "col"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / fileKey / description
      Previous value: -"Target connected file: bare key or Figma URL."New value: +"Figma key/URL."
    • addedInput schema / properties / gap
      Added value: +{
+  "maximum": 10000,
+  "minimum": 0,
+  "type": "number"
+}
    • addedInput schema / properties / icons
      Added value: +{
+  "minLength": 1,
+  "type": "string"
+}
    • removedInput schema / properties / jsx / description
      Removed value: -"JSX markup to render."
    • addedInput schema / properties / keepWrapper
      Added value: +{
+  "type": "boolean"
+}
    • changedInput schema / properties / label / description
      Previous value: -"Optional audit-log intent note."New value: +"Optional intent stored only as non-reversible audit metadata."
    • addedInput schema / properties / manifest
      Added value: +{
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / preset
      Added value: +{
+  "enum": [
+    "macbook-14",
+    "macbook-16",
+    "desktop",
+    "desktop-hd",
+    "iphone-15",
+    "iphone-15-pro-max",
+    "iphone-se",
+    "android",
+    "ipad-11",
+    "ipad-13"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / preview
      Added value: +{
+  "description": "Return a payload-free, non-mutating Command Plan.",
+  "type": "boolean"
+}
    • addedInput schema / properties / resizeProbe
      Added value: +{
+  "maximum": 2000,
+  "minimum": 1,
+  "type": "number"
+}
    • addedInput schema / properties / roots
      Added value: +{
+  "items": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 100,
+  "minItems": 1,
+  "type": "array"
+}
    • addedInput schema / properties / smartPosition
      Added value: +{
+  "type": "boolean"
+}
    • addedInput schema / properties / verify
      Added value: +{
+  "type": "boolean"
+}
    • addedInput schema / properties / x
      Added value: +{
+  "type": "number"
+}
    • addedInput schema / properties / y
      Added value: +{
+  "type": "number"
+}
    • removedInput schema / required
      Removed value: -[
-  "jsx"
-]
  2. First observedv0.5.1

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already indicate readOnlyHint=false and openWorldHint=true, so the description adds no new behavioral insight. It does not explain side-effects, scope of mutation, reversibility, or the confirm/preview flow. Given the open-world hint, more disclosure would be expected, but the description stays silent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single-sentence description is concise and free of filler, but it lacks structure and does not front-load critical information like the required confirm parameter or the preview mode. It is appropriately short but at the cost of essential detail.

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

Completeness1/5

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

For a tool with 21 parameters, no output schema, and low schema coverage, the description is severely incomplete. It fails to explain the difference between jsx and roots, the meaning of most parameters, or the behavioral implications. An agent would be guessing at almost every operational aspect.

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 only 19%, so the description must compensate, but it only mentions jsx and roots as primary inputs. The remaining 19 parameters (x, y, gap, preset, verify, confirm, etc.) are left unexplained. The description adds only marginal meaning beyond the schema, far from sufficient for correct invocation.

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 states the action (render), the inputs (JSX or roots[] batch), and the target (Figma). It distinguishes between two input modes, giving a specific verb-resource pair. However, it does not explicitly differentiate it from sibling tools like figma_run or figma_screenshot, so it misses the distinguishing context.

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 tool versus alternatives. No mention of alternatives, conditions, or exclusions. The description simply declares what the tool does without any contextual routing, leaving an agent without criteria for tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/KaiUweHella/figma-bridge-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server