Skip to main content
Glama
Sign In
OpenCode Figma MCP

OpenCode Figma MCP

by yhoyoex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_figma_design_from_url

Read a Figma design from a URL or file key through the Figma REST API, returning a code-oriented spec for a selected node or a file outline to choose frames.

Instructions

Read a Figma design through the Figma REST API (no plugin needed, requires FIGMA_ACCESS_TOKEN). Pass a Figma URL (figma.com/design//...?node-id=1-2) or fileKey + nodeId. With a node it returns the code-oriented spec; without a node it returns the file outline (pages and top-level frames) so you can pick one. Spec format: each node references shared values in styles by id (layout*, fill*, stroke*, effect*, text*). Layout values are CSS-like (flex, gap, padding, sizing fill/hug/fixed). exportAs: svg marks icons/vectors to export as assets instead of rebuilding them; assets lists icons and image fills to download with download_design_assets. designStyles and variables give design-token names to map onto the project's theme.

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

Input Schema

NameRequiredDescriptionDefault
urlNoFigma file/design URL, optionally with ?node-id=
nodeIdNoNode ID such as 1:2 or 1-2 (overrides node-id in url)
fileKeyNoFigma file key (alternative to url)
maxDepthNoMaximum depth of children to include (default: unlimited)
includeHiddenNoInclude hidden layers (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden and does well: it discloses the auth requirement, the two distinct return modes (spec vs file outline), the shared-styles indirection, the exportAs:svg marker, and the assets list. It stops short of pagination/rate-limit notes, keeping it at 4.

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?

Front-loaded with the core purpose and prerequisite, then the mode distinction. Dense but every sentence covers a distinct concept (mode, spec format, assets, tokens); the return-format detail is legitimately needed given no output schema.

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

Completeness4/5

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

For a complex, no-output-schema read tool the description covers return shapes, token/auth needs, and asset handling well. Minor residual gaps are pagination limits and how maxDepth/includeHidden affect the spec, but nothing essential to correct invocation is missing.

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, but the description adds value by showing the URL format example, the fileKey+nodeId alternative, and the behavioral consequence of supplying a node. maxDepth and includeHidden are left to the schema, which is acceptable.

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?

States a specific verb and resource ('Read a Figma design') plus the method ('Figma REST API, no plugin needed'). It is clearly distinguishable from siblings like read_my_design (plugin-based) and get_node_info by naming its URL-driven read path.

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

Usage Guidelines4/5

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

Explains the token prerequisite (FIGMA_ACCESS_TOKEN) and the node-vs-no-node selection rule with the purpose of each mode ('pick one'). It routes to download_design_assets for assets, though it doesn't explicitly contrast with read_my_design or get_design_context 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