Skip to main content
Glama
Sign In
figma-slides-mcp

figma-slides-mcp

by luan007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Create Table

create_table

Add a table to Figma Slides or FigJam using row and column counts, with optional cell width and height.

Instructions

Create a table (Slides/FigJam only)

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": {
      "parentId": "<parentId>",
      "rows": "<rows>",
      "cols": "<cols>"
    },
    "name": "create_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
colsYes
rowsYes
parentIdYes
cellWidthNo
cellHeightNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It only states the action ('create a table') without mentioning side effects, required permissions, return value, or dependency on parentId. For a mutation tool, this is a significant gap. It does not contradict any annotations, but it adds no behavioral context.

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 a single sentence with no redundant words. It conveys the essential purpose and platform restriction efficiently, earning its place.

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?

Given the tool's complexity (5 parameters, no annotations, no output schema), the description is severely underspecified. It lacks parameter explanations, relationship to sibling table tools, and behavior details. The only contextual element is the 'Slides/FigJam only' restriction. This is inadequate for correct selection and invocation.

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

Parameters1/5

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

The input schema has 5 parameters with 0% description coverage, and the description mentions none of them. The agent must rely solely on parameter names like parentId, rows, cols, cellWidth, and cellHeight, which is insufficient for correctly invoking the tool. The description fails to compensate for the lack of schema 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 uses a specific verb 'create' and a clear resource 'table', with the qualifier 'Slides/FigJam only'. This distinguishes it from sibling tools like insert_table_row, insert_table_column, and set_cell_content, which operate on existing tables. The purpose is unambiguous.

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 when a new table is needed, and the 'Slides/FigJam only' restriction provides a platform exclusion. However, it does not explicitly mention alternatives (e.g., using insert_table_row for adding rows later) or when NOT to use this tool beyond the platform limitation. Guidance is minimal and implied.

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

Deploy Server

Other Tools