Skip to main content
Glama

find

Search stored layer names and text in a saved Figma .fig file to locate matches and return IDs, paths, sizes, and text previews.

Instructions

Search stored layer names and text (case-insensitive). Returns ids, paths, local sizes and text previews. Does not expand instance children; use inspect on the instance. Copy inside instance overrides, text or boolean properties or swapped components is found by search, not find.

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": {
      "file": "<file>",
      "query": "<query>"
    },
    "name": "find"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesthe saved .fig: a local path (absolute recommended), or gs://bucket/object using gcloud; remote sources are unavailable with --root
nodeNosearch this stored subtree; default the document; use inspect for instance sublayers0:0
typeNoFigma node type, e.g. FRAME or TEXT
limitNo1-200 results, default 20; truncated signals more matches
queryYesliteral substring in a layer name or text

Output Schema

NameRequiredDescriptionDefault
rootYes
resultsYes
freshnessNoonly on no results in a mapped copy known to be stale: the freshness design report plus hint
truncatedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.13.1
    • addedOutput schema / properties / freshness
      Added value: +{
      +  "description": "only on no results in a mapped copy known to be stale: the freshness design report plus hint",
      +  "type": "object"
      +}
  2. Changed1 schema field changedv0.9.3
    • changedInput schema / additionalProperties
      Previous value: -trueNew value: +false
  3. Changed10 schema fields changedv0.7.2
    • addedInput schema / additionalProperties
      Added value: +true
    • changedInput schema / properties / file / description
      Previous value: -"the .fig file (File > Save local copy): an absolute path, or gs://bucket/object"New value: +"the saved .fig: a local path (absolute recommended), or gs://bucket/object using gcloud; remote sources are unavailable with --root"
    • addedInput schema / properties / file / minLength
      Added value: +1
    • addedInput schema / properties / limit / default
      Added value: +20
    • addedInput schema / properties / limit / maximum
      Added value: +200
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedInput schema / properties / node / default
      Added value: +"0:0"
    • changedInput schema / properties / node / description
      Previous value: -"search this subtree; default the document"New value: +"search this stored subtree; default the document; use inspect for instance sublayers"
    • addedInput schema / properties / query / minLength
      Added value: +1
    • addedInput schema / properties / query / pattern
      Added value: +"\\S"
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations provided, the description carries the disclosure burden and does well: it names the return contents (ids, paths, local sizes, text previews), declares case-insensitivity, and states a key limitation (no instance child expansion). It omits performance/rate or permission notes, but the essential behavior is covered.

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 tightly packed sentences with the core purpose front-loaded and zero filler. The terse phrasing in the last sentence ('Copy inside instance overrides... is found by search') is slightly dense but still parses.

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

Completeness4/5

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

An output schema exists so return values need no full explanation, and the description still sketches them. Scope limits and the sibling handoff to 'inspect' make it complete enough for correct invocation, with only minor gaps around pagination or truncation behavior.

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%, so the schema already documents all five parameters, including the query substring and node subtree semantics. The description only adds the case-insensitive matching note and the 'stored subtree' framing, which is marginal beyond structured data.

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 ('Search stored layer names and text') plus the matching mode (case-insensitive). It also distinguishes itself from the sibling 'search' by limiting scope to stored content that 'find' can see, so an agent can differentiate it 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?

Explicitly routes instance sublayer work to 'inspect' and clarifies that copy inside instance overrides, text/boolean properties, and swapped components belong to 'search' rather than 'find'. Clear context and exclusions are present, though no general when-to-use framing beyond these edge cases.

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