Skip to main content
Glama
Figma Local Bridge

Figma Local Bridge

by Miart

figma_get_design_context

Retrieve full design context for a Figma node to implement it in code, including layout, colors, text styles, component properties, and variable names.

Instructions

Full design description of a node for implementing it in code: layout (auto layout, padding, gap, sizing), fills/strokes/effects as hex, text runs with font/size/weight/line-height, style and variable names, component/instance info and properties.

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": "figma_get_design_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNo
nodeIdNoDefaults to the single selected node
fileKeyNoWhich connected Figma file to use: its fileKey (figma_whoami) or, when omitted, the only connected file. Required once more than one file is connected; figma_ping lists them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.36.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the kinds of data returned, including layout details, hex colors, text run properties, style/variable names, and component/instance information, but it does not describe depth traversal behavior, node selection behavior, permissions, failure cases, or other operational constraints.

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?

The description is a single, front-loaded sentence that states the main purpose first and then enumerates the returned content categories. It contains no filler and every listed category contributes to understanding what the tool returns.

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?

Given that there is no output schema and no annotations, the description does a reasonable job naming the major categories of returned design data. It is still incomplete for an agent deciding how to call the tool correctly, because it omits depth semantics, selection/default behavior, and any guidance on narrower sibling tools.

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

Parameters2/5

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

The schema already documents nodeId and fileKey, while depth is only constrained structurally with default/min/max and no semantic explanation. The description adds no parameter meaning at all, leaving the important depth parameter's effect on the returned design context unclear.

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?

The description clearly states that this tool returns a full design description of a Figma node for implementation in code, including concrete return categories such as layout, fills, text runs, and component data. It is more specific than a generic inspection tool, but it does not explicitly distinguish itself from close siblings like figma_get_layout_tree, figma_get_metadata, or figma_inspect.

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

Usage Guidelines3/5

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

The phrase 'for implementing it in code' implies the intended use case, which is helpful context. However, the description gives no explicit when-to-use guidance, no when-not-to-use conditions, and no named alternatives for narrower tasks such as layout-only or metadata-only retrieval.

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