Skip to main content
Glama
Sign In
conductor-figma

conductor-figma

by Dragoon0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

set_gradient_fill

Apply a two-color gradient fill to any Figma node using start and end hex colors, plus an optional angle.

Instructions

Set a gradient fill with a simple angle + 2 colors API.

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>",
      "startColor": "<startColor>",
      "endColor": "<endColor>"
    },
    "name": "set_gradient_fill"
  }
}

Input Schema

NameRequiredDescriptionDefault
angleNoGradient angle in degrees (default: 180)
nodeIdYesTarget node
endColorYesEnd color hex
startColorYesStart color hex

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.3.3

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It does not explain whether the gradient replaces the existing fill, what happens to unsupported node types, or what the tool returns. Mutation side effects are not disclosed.

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?

One concise, front-loaded sentence that conveys the operation, the resource, and the API's simplicity without filler. Every word earns its place.

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 simple four-parameter tool with fully documented schema, the description is serviceable: an agent knows what to call and with which parameter categories. However, with no annotations and no output schema, it lacks important behavioral context such as side effects and return behavior.

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 description coverage is 100%, so the schema already documents all parameters perfectly. The description adds minimal semantic value beyond listing 'angle + 2 colors', which merely echoes the schema structure.

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 ('Set') and identifies the exact resource ('gradient fill'), plus the distinctive API shape ('simple angle + 2 colors'). This clearly differentiates it from siblings like set_fill and set_image_fill.

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?

The tool's purpose implies when to use it: whenever a gradient fill with two colors and an angle is needed. However, it does not explicitly state when not to use it or mention alternatives like set_fill for solid fills or set_image_fill for image fills.

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