figlens

Overview Schema Source Related Servers Discussions Admin

find

Search a saved Figma .fig file by literal layer name or text to retrieve matching IDs, paths, sizes, and text previews; use inspect for instance sublayers.

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.

Input Schema

Name	Required	Description	Default
`file`	Yes	the saved .fig: a local path (absolute recommended), or gs://bucket/object using gcloud; remote sources are unavailable with --root
`node`	No	search this stored subtree; default the document; use inspect for instance sublayers	0:0
`type`	No	Figma node type, e.g. FRAME or TEXT
`limit`	No	1-200 results, default 20; truncated signals more matches
`query`	Yes	literal substring in a layer name or text

Output Schema

Name	Required	Description	Default
`root`	Yes
`results`	Yes
`truncated`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv0.7.2Oct 26, 2026

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"
```

First observedOct 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does most of it: it declares case-insensitive matching, the scope of the search (stored layers only, no instance expansion), what is returned, and that truncation signals more matches. It does not explicitly state read-only semantics or cost, but the search framing makes the read nature clear.

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?

Three short sentences, front-loaded with what is searched and what comes back, then the scope limit and the escape hatch. Nothing is redundant.

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 the brief return-value listing is a bonus rather than a requirement. For a five-parameter search tool the description covers matching semantics and scope well; only the relationship to the tree and nodes siblings is left for the agent to infer.

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 the baseline is 3, but the description adds genuinely new semantics: matching is case-insensitive, a fact the schema's 'literal substring' wording does not convey. It also explains the stored-subtree scope that governs the node parameter, which the schema only hints at.

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 gives a specific verb and resource: it searches stored layer names and text, case-insensitively, returning ids, paths, sizes and previews. It separates itself from the inspect sibling for instance children, though it leaves the boundary with tree and nodes implicit despite the bare name 'find'.

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?

It states an explicit exclusion and names the alternative: 'Does not expand instance children; use inspect on the instance', reinforced by the node parameter note. There is no guidance on when to reach for this versus tree or nodes, so it stops short of full routing guidance.

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

Deploy Server