Skip to main content
Glama
Figma Local Bridge

Figma Local Bridge

by Miart

figma_ping

Verifies the Figma plugin connection and reports the active page, connected files, and available read/write, Motion, and REST capabilities so you know what is open and which operations you can run.

Instructions

Health check and capability report. Verifies the plugin is paired, reports the active page and connected files (fileKey + name), and states what this process can do: local read/write/destructive mode, Motion (Beta) availability and playhead, whether the optional read-only Figma REST adapter is enabled, and the Figma-hosted features even that adapter does not proxy. Call it first when you do not know what is open or whether an operation is available.

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

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

A4.2/5.0
Behavior4/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 and does well: it discloses that this is a reporting/probe operation, enumerates the environment facts returned, and clarifies the scope limits of the optional REST adapter. It does not state latency/cost or confirm the call has no side effects, which keeps it below a 5.

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?

The purpose is front-loaded in the first five words and the enumerated capabilities are dense rather than padded. The single long colon-list sentence is information-rich but slightly heavy; splitting the capability inventory from the routing instruction would read even faster.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only one optional parameter, no annotations and no output schema, the description must explain what comes back, and it does by enumerating the reported items (pairing, page, fileKeys, mode, Motion, adapter). An agent can call it and interpret the result without any missing context.

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 description coverage is 100% and the single fileKey parameter is already fully documented, including its fallback to the only connected file. The description's note that it reports "connected files (fileKey + name)" and that "figma_ping lists them" reinforces the parameter's selection role but adds no syntax or format meaning beyond the schema, so the baseline 3 applies.

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?

"Health check and capability report" gives a specific verb-class plus resource, and the follow-up sentence enumerates exactly what it verifies: pairing state, active page, connected files, local read/write/destructive mode, Motion availability and playhead, REST adapter status. No sibling in the list performs a health/capability probe, so the agent can distinguish it immediately without opening the schema.

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?

"Call it first when you do not know what is open or whether an operation is available" is an explicit, actionable trigger condition that routes pre-flight discovery here instead of to inspect/read siblings. It lacks an explicit when-not clause (e.g., skip it once fileKey is already known), but the positive guidance is unambiguous.

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