Skip to main content
Glama
wenym8

figmingo-mcp

by wenym8

execute_plugin_command

Send single or batched Figma plugin commands to create, modify, and export nodes on the canvas, with queuing and progress tracking.

Instructions

Send a command envelope to the companion Figma plugin over the local bridge. Commands: create_frame, create_text, create_rectangle, set_fills, set_effects, set_auto_layout, insert_image, move_node, resize_node, delete_node, get_selection, get_file_info, get_page_children, export_node. Use commands for a batch executed sequentially in the plugin. Commands sent while the plugin is disconnected are queued (bounded) unless queue=false. Batches emit per-command progress heartbeats: the call fails only after idleTimeoutMs of silence or the total timeoutMs cap, and timeout errors list the command indexes confirmed applied on the canvas. export_node accepts an absolute params.outPath to save bytes to disk and return { path, bytes } instead of inline base64.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queueNoQueue while disconnected (default true); false = fail immediately.
paramsNoParameters for the single command.
commandNoSingle command name.
commandsNoBatch of commands; executed sequentially inside the plugin.
timeoutMsNoTotal cap in ms for the whole call once sent (default 300000 = 5 min). Batch heartbeats keep the call alive within this cap.
stopOnErrorNoBatch: stop on first error.
idleTimeoutMsNoMax silence in ms with no progress/result before failing (default 20000). Reset by every batch progress heartbeat.
Behavior4/5

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

With no annotations, the description discloses key behaviors: queuing while disconnected, batch progress heartbeats, timeout handling, and export_node's disk writing. However, it does not explicitly state whether commands have side effects (e.g., destructive ones like delete_node).

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 long but efficient. It front-loads the core purpose and command list, then adds behavioral details. Every sentence contributes value, though minor redundancy exists (e.g., queue mention twice).

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 7 parameters, nested objects, and no output schema, the description covers essential behaviors like batching, timeouts, and export. It could detail overall return structure more, but what's provided is sufficient for most use cases.

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 100%, but the description adds significant meaning: explains queue behavior, batch execution, timeouts, and export_node's return format. This goes beyond the schema's basic descriptions.

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 states the tool's purpose: 'Send a command envelope to the companion Figma plugin over the local bridge.' It lists specific supported commands, making it distinct from sibling tools like get_screenshot or bridge_status.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., compare_html_to_image, import_html_replica). Usage is implied through the command list, but no when-not-to or prerequisites are stated.

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/wenym8/figmingo-mcp'

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