UiChemy AI Website Creator

uichemy_move_section

Move a section to another page, or copy it there (copy: true), like the editor's section move/copy. Its layout and words go with it; a copy shares its words with the original, because copy belongs to the layout (give the copy its own words with uichemy_design_section replace, or swap its layout). Within one page use uichemy_reorder_sections or uichemy_duplicate_section.

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>",
      "pageName": "<pageName>",
      "index": "<index>",
      "toPage": "<toPage>"
    },
    "name": "uichemy_move_section"
  }
}

Input Schema

Name	Required	Description
`copy`	No	Leave the original where it is.
`index`	Yes	1-based, as uichemy_get_page lists them.
`toPage`	Yes
`pageName`	Yes	The page it is on now.
`position`	No	1-based place on toPage. Omitted = before its footer, or at the end.
`projectId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 29, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Adds genuinely non-obvious behavior beyond the annotations: a copy shares its text with the original because copy lives on the layout, and how to break that sharing (replace text or swap layout). Annotations already declare it is a safe, non-destructive mutation, so this is real added value rather than repetition; it never states that a move removes the section from the source page.

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?

Two sentences, front-loaded with the operation and the copy modifier; the sibling routing comes last where it belongs. The second sentence is dense and its clauses ('because copy belongs to the layout') read as a run-on, but 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 6-parameter cross-page mutation with no output schema, it covers the operation, the copy/layout sharing caveat, and the sibling alternatives. It omits failure modes (nonexistent target page, out-of-range index) and what a move does to the source page, which an agent would want before invoking.

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 67% and the schema already documents index (1-based, matching uichemy_get_page) and position defaulting to before the footer/end. The description only adds meaning for copy: true ('or copy it there'), and leaves toPage and projectId semantics to the schema.

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 — move or copy a section to another page — and immediately contrasts it with the in-page siblings (uichemy_reorder_sections, uichemy_duplicate_section). An agent can distinguish this from duplicate_section or add_section without opening any 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?

Explicitly routes in-page moves to uichemy_reorder_sections and in-page copies to uichemy_duplicate_section, and explains the copy-mode toggle. What's missing is preconditions (does toPage need to exist? does move fail on locked/global sections?) and guidance on when to omit position.

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?