Skip to main content
Glama

update_token

Override a design token's value locally and optionally push the change to Figma.

Instructions

Update a design token value in the local registry, and optionally push the change back to Figma.

Prerequisites: Token must already exist in the registry (use get_tokens to list names). To push to Figma, a plugin connection is also required.

Returns on success: Plain confirmation string Token "<name>" updated.

Error behavior: Returns isError if the token name is not found in the registry. If pushToFigma is true but Figma is not connected, the local update still succeeds — the push is silently skipped (no error thrown). To verify the push landed in Figma, capture a screenshot afterward.

Use this tool: to apply a token override (e.g. change a brand color for a client theme) and optionally propagate it to Figma immediately. For bulk token mapping to Tailwind, use sync_design_tokens instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesExact token name as it appears in get_tokens output (e.g. "Colors/Primary", "Spacing/XS"). Case-sensitive.
valuesYesMode-to-value map to merge into existing values (e.g. { "Light": "#FF0000", "Dark": "#FF6666" }). Only the modes you provide are updated — other modes are preserved.
pushToFigmaNoIf true and Figma is connected, push this token change to the Figma file immediately. Defaults to false (local registry only).
Behavior5/5

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

With no annotations, the description fully discloses behavior: local update always succeeds, push is silently skipped if Figma not connected, error on missing token, returns confirmation string, and suggests verifying with screenshot.

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?

Front-loaded with main purpose, then prerequisites, return, error, usage advice. Every sentence is necessary and well-placed, no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for a tool with 3 params and no output schema: explains return format, prerequisites, error handling, and usage hints. No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. Description adds value by explaining 'values' is a mode-to-value map that merges (only provided modes updated) and that 'name' is case-sensitive. This goes beyond the schema.

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 clearly states the tool updates a design token value in the local registry and optionally pushes to Figma. It distinguishes from sibling sync_design_tokens by noting the latter is for bulk token mapping to Tailwind.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states prerequisites (token must exist, plugin connection for push), error conditions (not found returns isError, silent skip if Figma not connected), and when to use this tool vs sync_design_tokens.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sarveshsea/memi'

If you have feedback or need assistance with the MCP directory API, please join our Discord server