Skip to main content
Glama
the-real-talk

the-real-talk

apply_style

Applies a local Figma style by ID or exact name to a node's text, effect, fill, stroke, or grid property, enabling consistent styling without manual selection.

Instructions

Apply a local style (by ID or exact name) to a node: TEXT, EFFECT, FILL, STROKE or GRID.

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>",
      "kind": "<kind>",
      "style": "<style>"
    },
    "name": "apply_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
styleYes
nodeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose useful traits: the style must be local (not library/remote), can be referenced by ID or exact name, and the node kind is constrained. It does not say whether an existing style of that kind is replaced, what happens if the name is ambiguous or the style is not found, or what permission/context is required for a mutation.

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?

A single sentence with the verb and constraint front-loaded and the kind list at the end; no filler or redundant restatement of the tool name.

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 three-required-parameter mutation with zero annotation and no output schema, the description identifies every parameter at a high level but omits side effects (replacement of existing styles), failure behavior, and any returned result. Adequate to attempt a call, not complete enough to predict its consequences.

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 0%, and the schema's 'style' param is merely a $ref to nodeId's non-empty string, so the description's 'by ID or exact name' clarification is genuinely valuable. The kind enum is already fully enumerated in the schema, and nodeId itself is still only implicitly explained as the target node.

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?

States a specific verb ('Apply') and resource ('a local style') plus the target ('a node') and enumerates the five applicable style kinds, so the operation is unambiguous. The 'local' qualifier also hints it does not pull from a shared library, though it never names a sibling to contrast with.

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 when-to-use or when-not-to-use guidance is given, despite siblings like set_text_style and set_text_range_style that plausibly overlap for text nodes. The only implicit guidance is the word 'local', leaving the agent to infer the boundary against those alternatives.

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