Skip to main content
Glama
Sign In
figma-free-mcp

figma-free-mcp

by haju-xp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_svg

Export a single Figma node as an SVG string, including all nested children. Returns the SVG markup for use in code or design workflows.

Instructions

Export a single node as an SVG string from Figma. Returns the SVG markup including all nested children.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "nodeId": "<nodeId>"
    },
    "name": "get_svg"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYesThe ID of the node to export as SVG

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.13

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries full burden. It states the output (SVG string with all nested children) and the action (export). However, it does not disclose any side effects, permissions, or limitations such as whether this triggers rendering or has size 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 two sentences, concise and front-loaded with the core purpose. Every word adds value, with no filler or redundancy.

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 simple export tool with one required parameter and no output schema, the description is mostly complete. It explains what is returned (SVG markup including children). Missing are potential error conditions or limitations, but overall adequate.

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 coverage is 100% with a single required parameter 'nodeId' described as 'The ID of the node to export as SVG'. The description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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 exports a single node as an SVG string from Figma, with specific verb 'export' and resource 'node as SVG'. It distinguishes itself from sibling tools like 'export_node_as_image' and 'get_image_from_node' by specifying the output format (SVG) and including nested children.

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 description implies usage for obtaining SVG markup of a node but does not explicitly mention when to use this tool over alternatives like 'export_node_as_image' or 'get_image_from_node'. No exclusion or alternative guidance is provided.

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