Skip to main content
Glama
AvYour

Figxel

by AvYour
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create shapes with text (FigJam)

figma_create_shapes_with_text
Idempotent

Create FigJam shapes with text for flowcharts, decisions, databases, and callouts—up to 200 per call, auto-sized unless width and height are set.

Instructions

FigJam shapes with text — flowchart steps, decisions, databases, callouts — 1–200 in one call, each sized to fit its text unless width and height are given (fitted). shape: one of 30 types in kebab case (square, ellipse, rounded-rectangle, diamond, triangle-up, parallelogram-right, eng-database, eng-queue, eng-file, eng-folder, hexagon, chevron, speech-bubble, …) or label: a numbered or lettered circle marker of 1–2 characters at a fixed size. color is a preset that sets fill, stroke and text together: black, dark-gray, gray, light-gray, white, and green, teal, blue, violet, pink, red, orange, yellow each with a light- form (light-green, …); or give hex fill / stroke / textColor instead. Laid out like figma_create_stickies (columns, gap default 40). Join them with figma_create_connectors. Row and column data is figma_create_table, never a grid of shapes. Editors: unverified in FigJam, Slides.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoLeft edge, in the parent's coordinates. Default: below what the parent holds; on the page, right of its content.
yNoTop edge, in the parent's coordinates.
gapNoSpace between shapes, px. Default 40.
shapesYes
columnsNoItems per row. Default: all in one row.
sessionNoOptional sessionId or file name, to pick a Figma file when more than one is connected.
parentIdNoA section or frame to put it in (id or Figma link). Default: the current page.
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. First observedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false) already declare the mutation/idempotency profile, and the description does not contradict them. It adds useful behavior beyond them: the 1–200 batch limit, text auto-fitting unless width/height are supplied, and that a preset sets fill, stroke and text together. It stops short of describing the returned node ids an agent would need for downstream chaining.

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?

Dense but front-loaded: the core action and batch limit lead, followed by shape/color semantics, then layout and alternatives. No filler sentences, though the single-paragraph block is heavy and would scan better with structure.

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 an 8-parameter creation tool with no output schema and 88% schema coverage, the description plus schema covers shape, color, sizing, layout and alternatives thoroughly. The main omission is any mention of what the call returns (node ids) for chaining into figma_create_connectors.

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 88%, so baseline is 3, but the description adds real meaning the schema lacks: it enumerates the `color` presets and their light- variants (the schema only calls them 'a coordinated preset'), lists concrete `shape` types, and clarifies that `label` produces a fixed-size 1–2 character circle marker. This substantially improves interpretation over the raw schema descriptions.

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+resource with scope: FigJam shapes with text, flowchart/decision/database/callout use cases, 1–200 per call. It actively distinguishes itself from siblings by naming figma_create_stickies (layout), figma_create_connectors (joining), and figma_create_table (tabular data, 'never a grid of shapes').

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?

Explicit alternatives and exclusions: join shapes with figma_create_connectors, use figma_create_table for rows/columns rather than a grid of shapes, and note that editors are unverified in FigJam and Slides. This routes the agent to the correct sibling for adjacent tasks.

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