Describe the connected FigJam board: file name, current page, node counts by type, content bounds, the user's viewport and selection. Call this first — it confirms the plugin is connected and tells you where there is free space to place new content.

List nodes on the current page, or inside a specific container. Returns id, type, name, text, position and size for each. Use this to understand an existing board before editing it.

Fetch full details for specific nodes, including text, fills, geometry and connector endpoints.

Return the nodes the user currently has selected in Figma. Use this when the user says "this", "these", or "the selected ones".

Search the current page for nodes whose text or name contains a substring (case-insensitive). Cheaper than listing a large board.

Render the page, a selection, or specific nodes to a PNG and return it as an image. This is how you visually check your own work — look at the result and fix layout problems before telling the user you are done.

Add one or more sticky notes. Stickies are the native FigJam unit for ideas, votes and retro items — prefer them over text nodes for anything a human might want to drag around.

Add FigJam shapes that carry a text label — the building block for flowcharts and architecture diagrams. For a whole diagram at once, prefer create_diagram, which also lays the shapes out and connects them.

Add free-floating text. Good for board titles, column headers and annotations; use stickies for content the user will rearrange.

Add syntax-highlighted code blocks. Useful for putting a snippet, schema or config next to the diagram that explains it.

Add named sections — the FigJam equivalent of a labelled swimlane or column. Pass a section id as parentId on other create tools to place content inside it.

Add a FigJam table and fill its cells. Pass cells as an array of rows, each row an array of strings; the first row reads as the header.

Draw connectors between existing nodes. Both endpoints must be ids of nodes that already exist — create the shapes first, then connect them.

Build a complete flowchart or graph in one call: nodes are placed with a layered layout, then wired together with connectors. This is the preferred tool for any multi-node diagram — it avoids the overlapping shapes you get from placing nodes by hand.

Refer to nodes by your own key strings; edges use those same keys.

Change text, colour, name or lock state on nodes that already exist. Only the fields you pass are touched; everything else is left alone.

Set absolute position, size, or parent container for existing nodes. Use it to tidy a board after generating content, or to move nodes into a section.

Permanently remove nodes from the board. This is destructive and the user cannot undo it from your side — confirm with them before deleting anything you did not create yourself in this session.

Scroll and zoom the user's Figma viewport onto specific nodes, and optionally select them. Call this after building something so the user is looking at it when you report back.

Build a complete architecture review board in one call: a system architecture diagram, a request lifecycle, an incident runbook, a service catalog table, config snippets, review stickies and a legend — about 200 nodes, in well under a second.

Use it to show what this server can do, or to check that a fresh install actually works. Pass mode "clean" to remove it again; everything it creates is tagged, so nothing else on the board is touched.