Skip to main content
Glama
Figma Local Bridge

Figma Local Bridge

by Miart

figma_search_design_system

Search components, styles, and variables by name or description across a local Figma file and library variable collections; every query word must match.

Instructions

Search components, styles and variables (local file, plus library variable collections) by name/description. All words in the query must match.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "figma_search_design_system"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindsNo
limitNo
queryYes
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.4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, but it does disclose one genuinely important behavioral trait: matching is conjunctive, so 'All words in the query must match' prevents an agent from assuming OR/keyword semantics. It says nothing about result ordering, truncation behavior, or what the response contains, which are real gaps for an unannotated, output-schema-less tool.

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 short sentences with no filler; the resource scope comes first and the matching rule second, which is the right order for an agent deciding whether to call it.

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?

For a 4-parameter search tool with no annotations and no output schema, the definition covers scope and match semantics but omits result-shape, default limiting, and how hits across components/styles/variables are combined. Minimum viable, with clear gaps an agent would have to discover by calling.

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 only 25% (only fileKey is documented), so the description must compensate, and it partly does: it clarifies the AND-matching semantics of 'query' and names the three kinds values that the enum already lists. 'limit' (default 25, max 100) is never mentioned, leaving one parameter with no semantic input anywhere.

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?

The description pairs the verb 'Search' with three concrete resources (components, styles, variables) and states the search key (name/description), so an agent knows exactly what is being queried. It stops short of differentiating itself from nearby siblings such as figma_design_system, figma_search, or 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 explicit statement of when to pick this over figma_design_system or figma_search, nor any exclusion or prerequisite beyond the implied 'searching by name'. The parenthetical about scope (local file plus library variable collections) hints at coverage but is not framed as usage guidance.

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