Skip to main content
Glama
arinspunk

Claude Talk to Figma MCP

by arinspunk

create_connector

Create connectors to link nodes or positions in FigJam diagrams. Connect stickies, shapes, or arbitrary points with arrows or lines, and customize line style, arrowheads, color, and thickness.

Instructions

Create a connector (arrow or line) in FigJam. Connectors can link two existing nodes by ID, or connect arbitrary canvas positions. Use this to draw flow arrows between stickies, shapes, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startNodeIdNoID of the node where the connector starts (omit to use startX/startY)
startXNoX position of the connector start point (used when startNodeId is not provided)
startYNoY position of the connector start point (used when startNodeId is not provided)
endNodeIdNoID of the node where the connector ends (omit to use endX/endY)
endXNoX position of the connector end point (used when endNodeId is not provided)
endYNoY position of the connector end point (used when endNodeId is not provided)
connectorLineTypeNoLine routing style (default: ELBOWED)
startStrokeCapNoArrowhead at the start (default: NONE)
endStrokeCapNoArrowhead at the end (default: ARROW)
strokeColorNoStroke color in RGBA format
strokeWeightNoStroke weight / line thickness
nameNoOptional name for the connector node
parentIdNoParent node ID. REQUIRED — server enforces this. Use page node ID for top-level elements. Get page IDs via get_pages tool.
Behavior2/5

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

No annotations provided, so description carries full burden. Mentions parentId is REQUIRED (server enforces) and how to get page IDs. However, lacks disclosure of side effects, auth requirements, rate limits, or what happens if parameters conflict. Limited transparency.

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?

Two sentences, front-loaded purpose, then brief parameter hint. No redundant information. Efficient and clear.

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?

Core purpose and two usage modes explained. Notes parentId requirement but lacks examples, format details for strokeColor, or clarification on mutual exclusivity of parameters. Adequate but not exhaustive for a 13-param tool.

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%, baseline 3. Description adds value by explaining two modes (node ID vs coordinates) and implicitly mapping parameters. Also notes default arrowhead at end. Provides context beyond schema.

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?

Clearly states verb 'create' and resource 'connector (arrow or line)'. Distinguishes from siblings by specifying target: 'FigJam' connectors, linking nodes or canvas positions. Purpose is unambiguous.

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?

Provides clear usage context: 'draw flow arrows between stickies, shapes, etc.' Does not explicitly exclude alternatives, but among many create siblings, this tool is distinct. Lacks explicit when-not-to-use, but context is sufficient.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/arinspunk/claude-talk-to-figma-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server