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

figma-slides-mcp

by luan007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Batch Operations

batch_operations

Run multiple Figma Slides commands in a single round-trip, using $N.field references to chain results and applying all changes as one undoable step.

Instructions

Execute multiple commands in one round-trip. Use "$N.field" to reference results from earlier commands (e.g. "$0.nodeId"). All execute as single undo step.

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": {
      "commands": "<commands>"
    },
    "name": "batch_operations"
  }
}

Input Schema

NameRequiredDescriptionDefault
commandsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses several key behaviors: round-trip execution, referencing results from earlier commands, and the single undo step. However, it omits important behavioral details such as failure handling or whether the batch is atomic, which are critical for a multi-command operation.

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 two sentences, front-loaded with the main purpose, and every sentence adds value. The reference example and undo-step note are concise and include no wasted words.

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?

For a batch wrapper, the description explains the core usage and undo behavior, which is adequate. However, it does not address error semantics (e.g., what happens if a command fails), execution order, or whether the command list is limited to specific commands. Given the complexity of a batch tool, this is a clear gap.

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 provides a concrete example of the reference syntax, but the schema already documents the 'params' object with the same pattern. Since schema description coverage is 0%, the description should compensate more; it does not explain the structure of the commands array or the meaning of the 'cmd' field beyond what the schema already provides.

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 tool executes multiple commands in one round-trip, distinguishing it from sibling tools that operate individually. The verb 'Execute' and resource 'multiple commands' are specific, and the phrase 'in one round-trip' highlights its batching purpose.

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?

The description implies usage when multiple commands need to be issued together, and it provides the key mechanism for referencing earlier results. However, it does not explicitly state when not to use this tool or mention alternatives, such as calling individual commands sequentially.

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