Skip to main content
Glama
Figma Local Bridge

Figma Local Bridge

by Miart

figma_get_figjam

Read a FigJam board to retrieve stickies, text-bearing shapes, connectors with endpoints, sections, and text; use it only for FigJam files, not regular Figma files.

Instructions

Read a FigJam board: stickies, shapes with text, connectors (with endpoints), sections and text. Fails in a regular Figma file.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "figma_get_figjam"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdNo
fileKeyNoWhich connected Figma file to use: its fileKey (figma_whoami) or, when omitted, the only connected file. Required once more than one file is connected; figma_ping lists them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.36.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses one failure mode (non-FigJam files) and implies a read-only operation, but says nothing about permissions/auth requirements, rate limits, or how large boards are handled.

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 with the action and its return content, then the key constraint. Nothing is padded or redundant.

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?

With no output schema and no annotations, the description does a decent job of listing returned content types and flagging the file-type constraint. It is still thin on scope — whether the whole board or a single node is read, and what an omitted nodeId defaults to — which matters for a 2-parameter tool with an unconstrained-by-description nodeId.

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 coverage is only 50%: fileKey is documented in the schema (fileKey from figma_whoami, or the sole connected file when omitted), but nodeId has only a regex pattern and no prose. The description never mentions either parameter, so it adds no meaning about what nodeId selects or what happens when it is omitted.

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 and resource ("Read a FigJam board") and enumerates the node types returned: stickies, shapes with text, connectors with endpoints, sections and text. The closing clause ("Fails in a regular Figma file") draws a hard line between this and the Figma-file readers among its siblings.

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?

Gives a clear negative condition — do not call this against a regular Figma file — which is the main routing decision an agent faces here. It stops short of naming the tool to use instead for regular files, so the agent must infer the alternative from the sibling list.

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