Skip to main content
Glama
southleft

figma-console-mcp

by southleft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

figma_get_library_components

Discover published components and variants from a shared Figma library file so you can find design-system elements before instantiating them in another file.

Instructions

Discover published components from a shared/team library file.

USE THIS when you need to use components from a published design system library (a different file than the one currently open). This bridges the gap between library discovery and instantiation.

WORKFLOW:

  1. Call this tool with the library file's URL or file key

  2. Browse the returned components — results include COMPONENT_SET (with variants array) and standalone COMPONENT types

  3. Use figma_instantiate_component with a VARIANT key (from the variants array inside a COMPONENT_SET result, NOT the component set key itself)

SEARCH NOTE: The query filter matches both component names AND descriptions. If you get unexpected results (e.g., "Accordion" when searching "Button"), verify the result name matches what you need — it may have matched on a description mention.

MULTI-FILE TIP: If you need to find a specific component and REST API search returns too many results, you can switch to the library file via figma_navigate, use figma_execute to find the exact component and its variant key, then switch back.

NOTE: Requires FIGMA_ACCESS_TOKEN to be set (uses the Figma REST API to read the library file).

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return (default: 25, max: 100)
queryNoSearch query to filter components by name (e.g., 'Button', 'Card'). Leave empty to get all components.
offsetNoOffset for pagination
libraryFileKeyNoThe file key of the library file (e.g., 'abc123'). Either this or libraryFileUrl is required.
libraryFileUrlNoThe URL of the library file (e.g., https://www.figma.com/design/abc123/My-Design-System). Either this or libraryFileKey is required.
includeVariantsNoInclude individual variant components (default: false, only returns component sets)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.46.0

TDQS

A4.6/5.0
Behavior4/5

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

No annotations exist, so the description carries the burden and does well: it discloses the FIGMA_ACCESS_TOKEN requirement, that reads go through the REST API, that results are COMPONENT_SET (with a variants array) or standalone COMPONENT, and the search matching quirk. It stops short of stating read-only semantics or rate-limit/pagination behavior explicitly.

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?

Front-loaded with the core use case and bolded section headers keep it scannable. It runs long, and the MULTI-FILE TIP is somewhat tangential, but nearly every line conveys actionable guidance.

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?

For a 6-param discovery tool with no output schema, the description supplies the auth prerequisite, the result shape, the variant-key pitfall, and the fallback path — everything an agent needs to call it correctly and act on the results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning beyond it: it warns that query matches names AND descriptions (the schema only mentions names), and explains that the usable variant key comes from the variants array rather than the component set key — a detail not captured in the schema.

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 — discovering published components from a shared/team library file — and immediately clarifies it covers a different file than the one open, which distinguishes it from figma_search_components and figma_get_component_details.

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

Usage Guidelines5/5

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

Explicit 'USE THIS when...' trigger, a numbered workflow, and named alternatives for edge cases (switch via figma_navigate + figma_execute when REST search is too noisy, then instantiate with figma_instantiate_component). When-to-use and how-to-chain are both covered.

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

Deploy Server

Other Tools