Set an explicit variable mode for a Figma node in a given collection. Override default modes to apply specific design token values per node.
Set an explicit variable mode for a node for a given collection.
| Name | Required | Description | Default |
|---|---|---|---|
| modeId | Yes | ||
| nodeId | Yes | ||
| collectionId | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description carries full burden. It implies a mutation but doesn't say whether it requires the node/collection to already exist, what happens to any existing mode assignment, whether it's reversible, or what it returns. Significant gaps for a write operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence with no waste, but it is under-specified rather than appropriately concise. Front-loading is fine; the problem is that there is essentially nothing after the verb.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No annotations, no output schema, 0% schema coverage, and three required parameters. The description does not fill any of those gaps, leaving the caller without enough to invoke it correctly or safely.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% for all three required parameters (nodeId, collectionId, modeId), and the description adds no format, ID-form, or constraint information. With 0% coverage the description must compensate, and it does not.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a verb (set) and resource (explicit variable mode for a node in a collection), but the phrase 'explicit variable mode' is jargon that isn't explained. It's distinguishable from siblings like set_variable_mode or bind_variable_to_property only by name, not by the description. Adequate but vague on what an explicit mode actually means.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance, no prerequisites, and no mention of alternatives despite many siblings in the variable/collection family (set_variable_mode, create_variable_mode, list_variable_collections). The agent must infer context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.