Skip to main content
Glama

figma_set_effects

Apply background blur, layer blur, drop shadow, or inner shadow effects to a Figma node, with optional clearing of existing effects.

Instructions

设置效果。第一版可写 BACKGROUND_BLUR / LAYER_BLUR / DROP_SHADOW / INNER_SHADOW。毛玻璃用半透明填充加 BACKGROUND_BLUR。

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": {
      "nodeId": "<nodeId>"
    },
    "name": "figma_set_effects"
  }
}

Input Schema

NameRequiredDescriptionDefault
clearNo
nodeIdYes
effectsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/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 and leaves key behavior unstated: whether the supplied effects array replaces all existing effects or appends, what the 'clear' flag does, and whether omitted effects mean no change. For a mutation tool with zero annotation coverage, this is a substantial gap.

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?

Three short sentences with no padding; the writable effect types are front-loaded and the practical tip trails them. The only weakness is that brevity is achieved partly by omitting necessary semantics.

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?

With no annotations, no output schema, and an undocumented nested effects structure, the description should settle replacement semantics and the 'clear' flag. It instead stops at listing effect types, leaving an agent unable to predict the result of a call.

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?

Schema description coverage is 0% for three parameters, and the description only repeats the effect-type list already encoded in the enum. It says nothing about 'nodeId', the 'clear' boolean, or whether 'effects' is a full replacement set — the parts an agent actually needs to fill in correctly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('设置效果') and enumerates exactly which effect types are writable in this version, so an agent knows the scope. It does not name or distinguish itself from the adjacent figma_set_fill, even though the frosted-glass recipe shows they interact.

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?

Usage is only implied: effects are applied to a node, and one concrete recipe is given (semi-transparent fill + BACKGROUND_BLUR for frosted glass). There is no guidance on when to use this versus figma_set_fill or figma_set_stroke, and no prerequisites or constraints mentioned.

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