Skip to main content
Glama
Sign In
conductor-figma

conductor-figma

by Dragoon0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

batch_style

Update fill, opacity, corner radius, font size, and weight across multiple nodes simultaneously, eliminating manual per-node edits.

Instructions

Apply style changes to multiple nodes at once.

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": {
      "nodeIds": "<nodeIds>",
      "changes": "<changes>"
    },
    "name": "batch_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
changesYesStyle changes: { fill, opacity, cornerRadius, fontSize, fontWeight, ... }
nodeIdsYesTarget nodes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.3.3

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral disclosure burden. 'Apply style changes' implies mutation but does not disclose whether existing style properties are overwritten, whether changes are reversible, or whether only specified properties are affected. For a batch mutation tool this is a significant transparency 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?

The description is a single, front-loaded sentence with no filler. It efficiently communicates the core operation, though it misses opportunities to add brief guidance without bloating the text.

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?

For a mutation tool with no annotations and no output schema, the description is too minimal. It does not clarify the effect on existing styles, the accepted value format for changes, or how it differs from the many sibling batch and style tools. An agent would need to inspect external examples to invoke it confidently.

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 both parameters. The description adds the phrase 'at once' but no new parameter-level meaning; the changes examples in the schema ('fill, opacity, cornerRadius, fontSize, fontWeight, ...') are the primary semantic content.

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 clearly states a specific verb and resource: 'Apply style changes to multiple nodes at once.' The 'multiple nodes' scope distinguishes it from the singular style tools like set_fill and set_stroke, though it doesn't explicitly name a sibling alternative.

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 usage context is provided. The description does not explain when to choose batch_style over the many related tools such as batch_set_corner_radius, batch_remove_effects, or batch_resize, nor does it state any exclusions or prerequisites.

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