Skip to main content
Glama
the-real-talk

the-real-talk

create_from_svg

Create vector nodes in Figma from an SVG string, such as icons like chevron, check, or burger. Set flatten to true to merge them into a single vector.

Instructions

Create vector nodes from an SVG string (icons: chevron, check, burger...). flatten true merges them into one vector.

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": {
      "svg": "<svg>"
    },
    "name": "create_from_svg"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
svgYes
nameNo
widthNo
heightNo
flattenNo
parentIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It discloses one behavior — that flatten merges nodes into a single vector — but says nothing about whether nodes are placed at a default position, what gets returned, or any constraints on the input SVG. For an 8-parameter mutation tool with no output schema, this is a significant shortfall.

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?

Two short sentences, front-loaded with the core action and with no wasted wording. The brevity is appropriate, though it comes at the cost of the parameter detail noted above.

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?

Given 8 undocumented parameters, no annotations, and no output schema, the definition is too thin. An agent cannot tell how x/y/width/height interact with the SVG's intrinsic dimensions, whether parentId is required for placement in a frame, or what the created node looks like.

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?

Schema description coverage is 0%, so the description must compensate for all 8 parameters. It only explains two of them: svg (by implication) and flatten. The placement parameters (x, y), sizing (width, height), naming, and parentId are entirely unexplained in both the schema and the description.

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: 'Create vector nodes from an SVG string.' This clearly separates it from the shape-creation siblings like create_rectangle or create_ellipse, though it doesn't explicitly name those alternatives.

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?

The icon examples ('chevron, check, burger') hint at intended use but stop short of when-to-use guidance. There is no statement about when to prefer this over creating shapes individually, and no prerequisites or exclusions.

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