figma-unlimited-mcp

Overview Schema Source Related Servers Discussions Admin

Create tables

create_tables

Add FigJam tables and fill their cells with row-major data. The first row becomes the header; optionally set coordinates to position the tables on the board.

Instructions

Add a FigJam table and fill its cells. Pass cells as an array of rows, each row an array of strings; the first row reads as the header.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "items": "<items>"
    },
    "name": "create_tables"
  }
}

Input Schema

Name	Required	Description	Default
`items`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the cell format and header behavior, which is useful, but does not mention side effects, permissions, or whether the operation is reversible. It also fails to note the array-wrapped input structure, which is a key behavioral aspect.

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?

The description is concise, with two sentences, and front-loads the core purpose. It includes essential cell formatting instructions without unnecessary verbosity. Every sentence adds value.

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

Completeness2/5

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

The schema has decent nested descriptions, but the description misses the critical fact that the input is an array of table objects (`items`), not a direct `cells` array. It also omits any mention of return value or behavior for multiple items. Given the lack of annotations and output schema, the description is insufficient for complete understanding and correct invocation.

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?

The description says to pass `cells`, but the actual top-level parameter is `items`, an array of objects. It fails to explain this nested structure, potentially leading to incorrect invocation. While the schema offers some documentation for x, y, cells, and parentId, the description adds little beyond the header row note and may even mislead about the required input shape.

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 'Add a FigJam table and fill its cells,' using a specific verb and resource. It distinguishes itself from sibling tools like create_shapes or create_stickies by focusing on tables. The additional detail about cell structure reinforces the purpose.

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 description implies usage for adding tables but does not explicitly state when to use this tool versus alternatives. It lacks exclusions or alternative tool suggestions, providing only implicit context that this is for tables.

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