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

figma-slides-mcp

by luan007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Create Slide

create_slide

Creates a new empty slide at 1920x1080 in Figma Slides. Set background fill, apply a theme, or add the slide to a specific row to structure your presentation.

Instructions

Create a new empty slide (fixed 1920x1080).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_slide"
  }
}

Input Schema

NameRequiredDescriptionDefault
fillsNoBackground fill. Hex "#ff0000" or Figma Paint array.
themeIdNoTheme ID to apply
rowIndexNoRow index to add slide to. Default: last row.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.3/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 carry the burden of behavioral disclosure. It mentions the slide is empty and fixed at 1920x1080, but does not disclose what happens to the presentation (e.g., where the slide is added), any side effects, or required permissions. This is a significant gap for a mutation tool.

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, front-loaded sentence with no wasteful words. It efficiently conveys the core purpose and a key constraint (fixed resolution).

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

Completeness3/5

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

The tool has 3 optional parameters and no output schema, and the description covers the basic behavior. However, it lacks guidance on the slide's placement in the presentation and any implications for the surrounding context. The schema fills in parameter details, but the description itself is minimal and leaves some ambiguity.

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

Parameters3/5

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

Schema coverage is 100%, with each parameter documented in the schema (e.g., fills, themeId, rowIndex). The description itself adds no parameter-specific meaning, so baseline 3 is appropriate. The schema descriptions are brief but provide adequate semantic info.

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 verb 'Create' and the resource 'new empty slide', and adds the specific constraint 'fixed 1920x1080'. This distinguishes it from siblings like duplicate_slide or create_slide_row, which create different entities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide any guidance on when to use this tool versus alternatives such as duplicate_slide, create_slide_row, or other creation tools. There is no context about prerequisites or placements, so the agent gets no help in selecting among siblings.

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