Skip to main content
Glama
arinspunk

Claude Talk to Figma MCP

by arinspunk
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Local

set_effects

Apply visual effects such as drop shadow, inner shadow, layer blur, or background blur to a Figma node using its ID and effect parameters.

Instructions

Set the visual effects of a node in Figma

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdYesThe ID of the node to modify
effectsYesArray of effects to apply

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changedv0.8.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / effects / items / additionalProperties
      Added value: +false
    • addedInput schema / properties / effects / items / properties / color / additionalProperties
      Added value: +false
    • addedInput schema / properties / effects / items / properties / offset / additionalProperties
      Added value: +false
  2. Changed4 schema fields changedv1.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / effects
      Added value: +{
+  "description": "Array of effects to apply",
+  "items": {
+    "properties": {
+      "blendMode": {
+        "description": "Blend mode",
+        "type": "string"
+      },
+      "color": {
+        "description": "Effect color (for shadows)",
+        "properties": {
+          "a": {
+            "description": "Alpha (0-1)",
+            "maximum": 1,
+            "minimum": 0,
+            "type": "number"
+          },
+          "b": {
+            "description": "Blue (0-1)",
+            "maximum": 1,
+            "minimum": 0,
+            "type": "number"
+          },
+          "g": {
+            "description": "Green (0-1)",
+            "maximum": 1,
+            "minimum": 0,
+            "type": "number"
+          },
+          "r": {
+            "description": "Red (0-1)",
+            "maximum": 1,
+            "minimum": 0,
+            "type": "number"
+          }
+        },
+        "required": [
+          "r",
+          "g",
+          "b",
+          "a"
+        ],
+        "type": "object"
+      },
+      "offset": {
+        "description": "Offset (for shadows)",
+        "properties": {
+          "x": {
+            "description": "X offset",
+            "type": "number"
+          },
+          "y": {
+            "description": "Y offset",
+            "type": "number"
+          }
+        },
+        "required": [
+          "x",
+          "y"
+        ],
+        "type": "object"
+      },
+      "radius": {
+        "description": "Effect radius",
+        "type": "number"
+      },
+      "spread": {
+        "description": "Shadow spread (for shadows)",
+        "type": "number"
+      },
+      "type": {
+        "description": "Effect type",
+        "enum": [
+          "DROP_SHADOW",
+          "INNER_SHADOW",
+          "LAYER_BLUR",
+          "BACKGROUND_BLUR"
+        ],
+        "type": "string"
+      },
+      "visible": {
+        "description": "Whether the effect is visible",
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "type"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / nodeId
      Added value: +{
+  "description": "The ID of the node to modify",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "nodeId",
+  "effects"
+]
  3. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are present, and the description does not disclose behavioral traits such as whether effects are replaced or merged, permissions needed, or side effects. This is insufficient 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, concise and to the point. While it could benefit from additional context, it is not verbose or redundant.

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?

Given the complexity of visual effects, the description is too brief. It does not explain that effects replace existing ones, confirm node requirements, or describe the return value (none provided). More context is needed.

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 has 100% description coverage for parameters, so the schema already provides detailed semantics. The tool description adds no extra meaning beyond stating the overall action.

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 action ('Set') and the resource ('visual effects of a node in Figma'), effectively distinguishing it from sibling tools like set_fill_color or create_effect_style.

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 versus alternatives (e.g., set_effect_style_id) or prerequisites (e.g., node existence). The description lacks context for appropriate usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/arinspunk/claude-talk-to-figma-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server