UiChemy AI Website Creator

uichemy_replace_text

Destructive

Replace a word or phrase everywhere it appears in the site's copy (every page, every section, including sections the Designer generated): a renamed product, a new phone number, a spelling. Case-insensitive unless matchCase. Pass pageName to limit it to one page. Overwrites the old wording in those places.

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": {
      "projectId": "<projectId>",
      "find": "<find>",
      "replace": "<replace>"
    },
    "name": "uichemy_replace_text"
  }
}

Input Schema

Name	Required	Description
`find`	Yes
`replace`	Yes
`pageName`	No	Only this page. Omit for the whole site.
`matchCase`	No
`projectId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare a destructive, non-read-only operation, and the description adds valuable behavioral detail: it touches every page and section including Designer-generated ones, defaults to case-insensitive matching, and overwrites the old wording. It still omits matching boundaries, undo/reversibility, and whether non-copy content is affected.

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?

Front-loads the core action and scope, then layers in case behavior, page limiting, and overwrite semantics. The examples are short and useful; no sentence is wasted.

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 destructive bulk replacement tool with no output schema, the description supplies the key scope and matching defaults an agent needs to call it safely. It is only missing details about irreversibility/undo and precisely what counts as 'copy' across the site.

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 only 20%, so the description must carry more of the parameter burden. It usefully clarifies pageName scoping and matchCase behavior, but find and replace semantics remain ambiguous: whether matching is literal substring, whole-word, or regex-like, and whether an empty replacement deletes text.

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 — replace text — with explicit global scope: 'everywhere it appears in the site's copy.' The examples and the 'every page, every section' phrasing make it clearly a bulk replacement tool, distinguishable in scope from single-target siblings like uichemy_set_text.

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?

Gives clear usage context with concrete examples (renamed product, new phone number, spelling) and explains how to narrow scope with pageName. It does not name alternatives such as setting text at a single target or reading text first, nor does it state when not to use this tool.

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

All UiChemy AI Website Creator tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?