Skip to main content
Glama
AvYour

Figxel

by AvYour
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Find and replace text

figma_find_replace_text
Idempotent

Find and replace text across Figma text layers, sticky notes, shapes, connector labels, table cells, and code blocks, scoped to page, selection, or a node subtree.

Instructions

Find and replace across text: TEXT nodes and, on a board, stickies, shapes, connector labels and table cells (an item names the node, plus cell "row,column"); code blocks with includeCode. Other styled runs in a text are kept. Scope it to the page (default), the selection, or a subtree by nodeId. Returns per-item results: items: [{ id, ok, error? }] — one node failing does not fail the call. Editors: Design; unverified: FigJam, Slides.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
findYes
regexNoTreat `find` as a regular expression. Default false.
scopeNoDefault "page".
nodeIdNoSubtree root when scope is "subtree".
replaceYesThe new text; "" deletes each match.
sessionNoOptional sessionId or file name, to pick a Figma file when more than one is connected.
includeCodeNoAlso replace inside code blocks' code. Default false.
caseSensitiveNoDefault true.
idempotencyKeyNoCaller-owned retry key, ≤128 chars. Re-calling with the same key never executes twice: it returns the existing result, or waits for the op still in flight. Supply your own for anything large — if the MCP client times out (rather than the bridge), only a key you chose can be used to retry safely.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing that other styled runs are preserved, that results are per-item (items: [{id, ok, error?}]) so one failure does not fail the whole call, and notes editor support with FigJam/Slides unverified. These are meaningful behavioral traits not carried by the annotations.

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?

The purpose is front-loaded and the paragraph is dense but mostly earns its place. It is somewhat packed with parenthetical asides, but not padded or repetitive.

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 9-parameter mutation tool with no output schema, the description covers return shape, partial-failure semantics, scope mechanics and editor compatibility. It leaves minor gaps (e.g., regex/case-sensitivity interaction, auth needs) but is largely complete.

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?

With schema coverage at 89% the baseline is 3, but the description adds genuine value by documenting the table `cell` "row,column" coordinate format and the includeCode behavior on code blocks, details not present in the schema properties.

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?

States a clear verb+resource (find and replace across text) and enumerates the node types covered, including TEXT nodes, stickies, shapes, connector labels and table cells. It is distinguishable from bulk-rename or set_text siblings, though it never explicitly names an alternative tool.

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?

The description lists scope options (page/selection/subtree) but offers no explicit when-to-use or when-not-to-use guidance, nor does it name an alternative tool. The agent must infer appropriate contexts on its own.

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