UiChemy AI Website Creator

uichemy_update_designed_section

Destructive

Replaces a section on the user's page with the redesign you wrote after uichemy_design_section with replace: same page, same position, new design. Its previous code, copy and pictures are replaced and not kept, so confirm with the user before rewriting a section they edited by hand. The file is checked like uichemy_add_designed_section and its copy becomes editable slots.

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>",
      "kind": "<kind>",
      "templateId": "<templateId>",
      "code": "<code>",
      "replace": "<replace>"
    },
    "name": "uichemy_update_designed_section"
  }
}

Input Schema

Name	Required	Description
`code`	Yes	The complete section .jsx file.
`kind`	Yes	Section kind: hero, features, testimonials, pricing-table, cta, faq, team, gallery…
`replace`	Yes	1-based section being redesigned.
`pageName`	No	Defaults to Home.
`projectId`	Yes
`templateId`	Yes	The id uichemy_design_section gave.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

removedInput schema / properties / name

Removed value: -{
-  "description": "What it is called on the canvas. Defaults to the kind.",
-  "type": "string"
-}

AddedOct 29, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true, but the description goes further: it names exactly what is lost (previous code, copy and pictures are replaced and not kept), states the file is validated like uichemy_add_designed_section, and explains that copy becomes editable slots. That is concrete consequence-level detail an agent cannot get from 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?

Three sentences, all load-bearing: purpose and position, destruction and confirmation, validation and slot behavior. The opening sentence is slightly tangled with the backticked `replace` mid-clause, but nothing is padded or repeated.

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 mutation with no output schema and 6 parameters, the description covers the important gaps: what is destroyed, the prerequisite design step, the confirmation requirement, and validation behavior. It does not describe what comes back on success or failure, which is the only remaining omission.

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 83%, so most parameters are self-documenting and the baseline is 3. The description adds real meaning on top by tying `replace` to "same page, same position" and `templateId` to the id returned by uichemy_design_section, clarifying the cross-tool contract that the schema only gestures at.

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 ("Replaces a section on the user's page") and immediately frames it as the follow-up to uichemy_design_section with `replace`, which separates it from uichemy_add_designed_section and uichemy_replace_section. An agent can tell what this does 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?

Gives a clear prerequisite chain (write the redesign via uichemy_design_section, then call this with the templateId it returned) and an explicit caution to confirm with the user before overwriting hand-edited sections. It does not, however, distinguish itself from the sibling uichemy_replace_section, which is the one real ambiguity left for an agent choosing a 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?