Skip to main content
Glama
Figma Local Bridge

Figma Local Bridge

by Miart

figma_get_selection

Returns the current Figma selection from plugin memory, avoiding a round trip into Figma. Pass fileKey when multiple files are connected.

Instructions

Current selection. Answered from memory — the plugin pushes selectionchange, so this costs no round trip into Figma. With several files connected, pass fileKey.

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_selection"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the whole burden. It does disclose a genuine behavioral trait — the value comes from a locally pushed selectionchange event rather than a Figma round trip — but says nothing about staleness, what happens when the selection is empty or multi-node, or whether the call can fail with no connected file.

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?

Three short sentences, front-loaded with what is returned and immediately followed by the low-cost property an agent cares about. The opening fragment is slightly clipped but no sentence is wasted.

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?

There is no output schema, so the description is the only place the return value could be characterized — and it never says what a selection object contains or how empty/multi-node selections appear. For a simple zero-required-parameter read, it is adequate but leaves the response shape unexplained.

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?

Schema coverage is 100% and the fileKey description already explains the single-file fallback and points at figma_whoami/figma_ping. The description's fileKey sentence largely restates the schema, adding only a light reinforcement of the multi-file condition, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Current selection" names the resource returned, and the memory/selectionchange sentence makes clear this is a cached read of the live selection state. It is terse and lacks a verb, but an agent can tell it apart from figma_set_selection, which mutates rather than reports.

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

Usage Guidelines3/5

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

The only usage guidance is conditional on connected-file count ("With several files connected, pass fileKey"). Nothing says when to prefer this over figma_get_design_context, figma_inspect, or figma_get_metadata for inspecting what the user has selected.

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