Skip to main content
Glama
Figma Local Bridge

Figma Local Bridge

by Miart

figma_get_libraries

Retrieve variable collections and libraries available in a connected Figma file, including local collections and those enabled from team libraries; pass a fileKey when multiple files are connected.

Instructions

Variable collections available in this file: local ones and those enabled from team libraries.

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

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

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it only discloses collection scope (local vs. team-library enabled). It says nothing about whether this is read-only, whether disabled/remote libraries are excluded, whether the result is paginated, or what a returned entry contains.

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?

It is a single short clause with zero filler and the scoping detail is front-loaded. The only structural flaw is that it is an incomplete sentence, which costs it the top score on clarity.

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

Completeness2/5

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

The tool has no annotations and no output schema, so the description is the only source of behavioral information, and a one-clause fragment does not cover return shape or usage context. For a listing tool whose output an agent must reason about, this is materially under-specified.

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?

The single optional fileKey parameter is fully documented in the schema (100% coverage), including how to obtain it and the multi-file requirement, so the description does not need to compensate. Baseline 3 applies since the description adds no meaning beyond the schema.

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

Purpose3/5

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

The description names the resource (variable collections) and scopes it to local plus team-library-enabled collections, which is more specific than the bare name. However it is a noun phrase with no verb, so the agent must infer that this is a read/list operation rather than a filter or mutation, and it never distinguishes itself from figma_get_variable_defs.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of which sibling to pick when the goal is variable definitions versus collections. The agent is left to infer the boundary against figma_get_variable_defs and figma_get_metadata entirely on its own.

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