Skip to main content
Glama
Sign In
conductor-figma

conductor-figma

by Dragoon0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

generate_stylesheet

Generate a complete stylesheet from a Figma design file in CSS, SCSS, or Tailwind format.

Instructions

Generate a complete stylesheet from a design file.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "generate_stylesheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoOutput format (default: css)
pageIdNoPage ID

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?

No annotations are provided, so the description must disclose behavior on its own. It only says it generates a stylesheet; it does not say whether the operation is read-only, whether it acts on the current page or entire document, what 'complete' includes, or what the returned output contains. This is a significant transparency gap for a tool with no annotation support.

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, focused sentence that communicates the core purpose efficiently. It does not add unnecessary words, though it could be structured to also include key usage caveats without much bloat.

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?

With no output schema and no annotations, the description should explain what a generated stylesheet looks like, how format and pageId affect the result, and whether this reads the whole document or a selected page. None of that is present, so an agent cannot fully predict the tool's behavior or return value.

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?

The schema coverage is 100%, with both format and pageId documented in the input schema. The description adds no parameter-level meaning beyond that, but because the schema already handles semantics, the baseline 3 is appropriate.

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 and resource: 'Generate a complete stylesheet from a design file.' It is clear about the action and object. However, it does not differentiate itself from siblings like export_design_specs, export_color_palette, or read_node_css, so an agent must infer where the boundaries lie.

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?

There is no guidance on when to use this tool versus alternatives. The description implies it is for generating a whole stylesheet, but it never states explicit when-to-use, when-not-to-use, or alternative tools. This leaves the agent to guess among many export/generation siblings.

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