Skip to main content
Glama
Sign In
Figxel

Figxel

by AvYour
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create line

figma_create_line
Idempotent

A straight line: dividers, connectors, arrows, underlines, decorative strokes. length in px from (x, y), turned by angle degrees (0 = to the right, 90 = up).

Instructions

A straight line: dividers, connectors, arrows, underlines, decorative strokes. length in px from (x, y), turned by angle degrees (0 = to the right, 90 = up). cap decorates both ends: arrow, arrow-filled, triangle, circle, diamond, round, square. For a divider inside an auto-layout, a 1 px figma_create_rectangle with sizing: { horizontal: "fill" } stretches with the column; a line keeps its length. Editors: Design; unverified: FigJam, Slides.

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
capNo
nameNo
angleNoDegrees, default 0.
colorNoDefault #000000.
forceNoOverwrite on purpose. A write to a node someone changed after you last read it is refused (STALE); read it again and resend instead. Pass true only when the person said to overwrite their edit.
lengthYes
weightNoStroke weight in px, default 1.
sessionNoOptional sessionId or file name, to pick a Figma file when more than one is connected.
parentIdNo
dashPatternNoDash and gap lengths, e.g. [4, 4].
idempotencyKeyNoCaller-owned retry key, ≤128 chars. Re-calling with the same key never executes twice: it returns the existing result, or waits for the op still in flight. Supply your own for anything large — if the MCP client times out (rather than the bridge), only a key you chose can be used to retry safely.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • addedInput schema / properties / force
      Added value: +{
+  "description": "Overwrite on purpose. A write to a node someone changed after you last read it is refused (STALE); read it again and resend instead. Pass true only when the person said to overwrite their edit.",
+  "type": "boolean"
+}
  2. First observedv0.1.1

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false and closed-world, so the safety profile is covered. The description adds real value beyond them — geometry semantics for `length`/`angle` and the auto-layout resize behavior — but says nothing about the returned node identity, default placement when `parentId` is omitted, or whether the new line is selected.

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 and dense — the use cases, then geometry, then the rectangle alternative, then environment caveats. Every sentence carries information, though the telegraphic fragment style ('A straight line: ...') costs a little readability and the auto-layout sentence is long.

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 13-parameter mutation tool with no output schema, the description covers the geometry that actually determines the result and the environment constraints. It could have closed the loop on what is returned and on default parenting, but the schema's descriptions plus annotations fill most of the remaining space.

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?

With only 54% schema coverage the description does meaningful work: `length` is quantified as px from (x, y), `angle` as degrees with 0=right and 90=up, and `cap` is enumerated with the fact that it decorates both ends. However `name` and `parentId` are documented in neither place, and gaps remain on whether x/y are absolute or parent-relative.

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?

Opens with a concrete resource plus a list of canonical use cases (dividers, connectors, arrows, underlines, decorative strokes), which pins down the shape type immediately. It also names the sibling it competes with (figma_create_rectangle) and the condition that separates them, so an agent can route without opening either schema.

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

Usage Guidelines5/5

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

Explicitly says when to use a rectangle instead: for a divider inside an auto-layout, a 1 px rectangle with `sizing: { horizontal: "fill" }` stretches while a line keeps its length. It also states environment coverage (Design supported; FigJam and Slides unverified), which is exactly the qualification an agent needs before committing.

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