Loading ToolBench

Reading the current corpus…

figma-design-bridge MCP server · F · ToolBench

← Browse

figma-design-bridge

github.com/evidence-codes/figma-design-bridge

MCP server that lets an agent write design specs onto a Figma canvas

2026-07-28+STDIO5 tools

49/100

Definition Quality57

Protocol Readiness50

Supportability35

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence

Current-spec patterns detected

Summary

Server has 5 tools with basic descriptions but critical gaps in schema completeness and parameter documentation. Tool names follow verb_noun convention (figma_status, render_screen, create_variables, list_screens, delete_screen) which is good. However, most tools lack detailed input parameter schemas, only render_screen and create_variables show partial schema structure (generic 'object' type with minimal field documentation). No output schemas are documented. Error handling is minimal; no recovery guidance provided. Parameter descriptions are absent or generic. The server is STDIO-only, which caps protocol readiness at 50 regardless of definition quality.

Tools (5)

create_variableswritesource verified60/100

Create or update a Figma variable collection of colours. Run this before rendering screens so the design tokens exist as real variables.

delete_screendestructivesource verified60/100

Remove a screen previously rendered by this bridge, by its key.

figma_statusread onlysource verified53/100

Check whether the Figma plugin is connected and which file it has open. Call this first if anything seems wrong.

list_screensread onlysource verified52/100

List the screens this bridge has rendered into the current file, with their keys.

render_screenwritesource verified58/100

Render a screen onto the Figma canvas from a typed spec. Frames become auto-layout frames, text becomes real text nodes. Re-rendering the same 'key' replaces the previous version in place rather than duplicating it.

Issues (5)

CRITICALconstrained-input ↗

Input schemas are missing or incomplete. figma_status and list_screens have empty {} schemas with no parameter documentation. render_screen and create_variables show only generic 'object' type with vague descriptions ('ScreenSpec', 'VariableSpec') but no actual field definitions, types, or constraints visible in source.

figma_statuslist_screensrender_screencreate_variables

CRITICALtool ↗

No output schemas documented. LLMs cannot predict what fields render_screen, create_variables, or list_screens return, forcing them to guess at downstream field names and types. This breaks tool chaining.

render_screencreate_variableslist_screens

HIGHtool-description ↗

Parameter descriptions are missing or generic. delete_screen accepts 'key' with description 'The key of the screen to delete' but no format, length, or example guidance. render_screen's 'spec' parameter description is just 'ScreenSpec - contains key, name, width, background, x, y, and root node tree', not actionable for an LLM.

Recommendations

Define complete input schemas for all tools. For render_screen, expand the 'spec' parameter to show actual ScreenSpec fields (key: string, name: string, width: number, background: string, x: number, y: number, root: object) with type and description for each.
Document output schemas. Specify what render_screen returns (e.g. {frame_id: string, name: string, url: string}), what create_variables returns (e.g. {collection_id: string, mode: string, color_count: number}), and what list_screens returns (e.g. {screens: [{key: string, name: string, frame_id: string}], total: number}).
Add parameter constraints and formats. For delete_screen's 'key' parameter, specify format (alphanumeric, max 100 chars). For render_screen's 'spec', document required vs optional fields and valid value ranges (e.g. width: 1 - 4000, x/y: -10000 - 10000).
Enhance error messages with recovery guidance. When plugin is not connected, return: 'No Figma plugin connected. Open your file in the Figma desktop app, run the Design Bridge plugin, and leave its panel open. Then retry figma_status.' When spec is invalid, return: 'Invalid ScreenSpec: missing required field "key" or "root". Ensure spec contains {key, name, width, background, x, y, root}.'
Add a confirm_delete_screen tool or dry-run mode to delete_screen. Before destructive operations, return {action: 'confirm_delete', screen_key: '...', screen_name: '...'} and require explicit confirmation via a separate confirm_action call.

Score history

Overall score trend

First recorded score · v2 rubric

49/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	49	2026-07-28+	v2