Skip to main content
Glama
lama-assaf

conductor-figma

by lama-assaf

export_tokens

Export design tokens from Figma into JSON, CSS, SCSS, or Tailwind format for development integration.

Instructions

Export all design tokens as JSON, CSS custom properties, SCSS, or Tailwind config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoExport format (default: json)
Behavior2/5

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

No annotations provided. Description does not disclose behavioral traits like scope (global vs file-level), read-only nature, or side effects.

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?

Single, well-structured sentence with key information front-loaded. No unnecessary words.

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?

Adequate for a simple one-parameter tool, but lacks scope clarification (e.g., exports from current file or entire library) and usage context among similar export tools.

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 covers format enumeration completely. Description merely restates formats in text, adding no extra meaning or validation context.

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?

Clearly states export of all design tokens in multiple formats. Differentiates from specific token export siblings like export_color_palette, but could explicitly contrast with them.

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 guidance on when to use this tool vs alternatives such as export_color_palette or export_spacing_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/lama-assaf/conductor-figma'

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