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

figma-slides-mcp

by luan007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Duplicate Slide

duplicate_slide

Clone any slide with its full content in Figma Slides to reuse or create variations.

Instructions

Clone a slide with all content

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": {
      "slideId": "<slideId>"
    },
    "name": "duplicate_slide"
  }
}

Input Schema

NameRequiredDescriptionDefault
slideIdYesSlide to duplicate

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 present, so the description bears the full responsibility. 'Clone a slide with all content' indicates the action but does not disclose side effects such as placement of the new slide, whether the original remains unchanged, or what happens to slide properties and notes. 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 five-word sentence, front-loaded with the verb 'Clone'. There is zero waste and it is easy to parse.

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 is simple with one required parameter and no output schema. The description adequately states the action, but it does not mention what the tool returns (e.g., new slide ID) or where the duplicate is inserted. This missing context prevents a higher score, yet it remains minimally usable.

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?

The input schema already documents slideId with description 'Slide to duplicate', giving 100% coverage. The tool description adds no parameter-specific information beyond the general 'all content' context, so it stays at the baseline of 3.

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 'clone' with resource 'slide' and adds scope 'with all content'. This clearly distinguishes it from create_slide (new slide) and clone_node (clone a node).

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?

No guidance is provided on when to use this tool over alternatives. It does not mention sibling tools or exclusions, leaving the agent to infer when to call it.

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