Skip to main content
Glama

figma_batch

Execute multiple Figma operations in one request for repetitive tasks like table rows, list items, or grid cells. Each operation runs independently; failures are reported without blocking others.

Instructions

Execute multiple Figma operations in a single bridge round trip. Use this for repetitive structures — table rows, list items, grid cells, repeated cards — where individual calls would be impractical. Each operation in the array is a { tool, params } object using the same tool names as the individual tools (without the figma_ prefix internally). Returns an array of results in the same order as the operations. A failed operation is reported with { ok: false, error } and does not stop subsequent operations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationsYesArray of operations to execute. Each: { tool: string, params: object }. tool values: "create_frame", "create_text", "create_rectangle", "set_component_text", "set_layout_sizing", "set_text", "set_node_fill", "set_visibility", "insert_component".
Behavior5/5

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

Discloses batched execution, error behavior (failed ops reported with error, do not stop subsequent ops), and return format, adding value beyond annotations which only provide hints.

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

Conciseness5/5

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

Efficiently conveys purpose, usage, structure, and error handling in a well-organized paragraph without redundancy.

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?

Covers operation format, error handling, and return, but could explicitly mention that operations are executed sequentially for full clarity given the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds significant meaning beyond schema by explaining tool values without 'figma_' prefix and clarifying the structure of each operation object, even though schema coverage is 100%.

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?

Clearly states it executes multiple Figma operations in one round trip, with specific use cases (table rows, list items, etc.), distinguishing it from individual sibling tools.

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?

Explicitly recommends using for repetitive structures where individual calls are impractical, providing context on when to use, though it doesn't outline when not to use.

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/miapre/mimic-ai'

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