Skip to main content
Glama
tokensqueezer-mcp

tokensqueezer-mcp

search_layers

Find layers by name, text content, or semantic type in the current Figma selection tree and return full breadcrumb paths.

Instructions

Search layers by name, text content, or semantic type in the current Figma selection tree and return full breadcrumb paths.

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": "search_layers"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoFilter by layer category. Defaults to all.
queryYesCase-insensitive search term matched against layer names and text content.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does signal that this is a read-style lookup returning breadcrumb paths, which is useful. However it omits whether an active selection is required, what happens with an empty selection, and any result limits or ordering, all of which matter for a tree-scoped search.

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?

A single front-loaded sentence with the scope and return value stated up front and zero filler. Nothing could be removed without losing information.

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?

For a two-parameter search tool with no output schema, the description covers the target corpus, the matching criteria, and the return format (breadcrumb paths). It falls just short of complete because it never states the precondition of an existing selection or how empty/no-match results behave.

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 coverage is 100%, so both parameters are already documented, establishing a baseline of 3. The description adds marginal value by mapping the query to names and text content and clarifying that "semantic type" corresponds to the type filter, but adds no syntax, matching, or defaulting detail beyond the schema.

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 ("Search") and resource ("layers") plus a clear domain scope ("current Figma selection tree") and even states the return shape ("full breadcrumb paths"). It does not explicitly contrast itself with any sibling, but the action is distinct enough from siblings like add_figma_annotation or compare_selections that confusion is unlikely.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the phrase "current Figma selection tree" tells the agent this only makes sense when a selection exists, but there is no explicit when-to-use/when-not-to-use guidance and no named alternative for broader searches outside the selection. The agent must infer the prerequisite.

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