Xodia

Rename or move a folder

update_folder

Destructive

Renames a folder (name) or moves it (to: a new slug or parent), with everything under it in one change: every page's route and file, sub folders, collections whose URL folder is inside it, the internal links to all of them, redirects for the published ones and the site plan. dryRun says what would change first. Addresses are lowercase words with dashes, up to 5 folder levels; an address another page, folder or collection uses is refused with address_clash and the reason (a collection's item level, /blog/, belongs to its items unless the collection reserves that slug). Writes unsaved changes the user reviews and saves in Xodia, and the site plan follows in the same change.

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": {
      "path": "<path>",
      "projectId": "<projectId>"
    },
    "name": "update_folder"
  }
}

Input Schema

Name	Required	Description
`to`	No	A new address: another slug ("what-we-do") or another parent ("company/services"); every page, sub folder and collection under it moves
`name`	No	A new name (the address stays)
`path`	Yes	The folder to change
`branch`	No	Optional branch; default the branch the workspace has open
`dryRun`	No	Only say what would change; writes nothing
`redirect`	No	Omit: redirects only for published pages and collections that move; true: for every one; false: none
`projectId`	Yes	Project id from list_projects

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The annotations only flag destructive=true; the description goes well beyond that by enumerating exactly what is destroyed or rewritten (routes, files, sub folders, collections whose URL folder is inside it, internal links, redirects, site plan) and by disclosing that writes are staged for the user to review and save in Xodia rather than applied immediately. It also names the failure mode (address_clash) and the clash rule for collection item levels.

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 core operation is front-loaded in the opening clause and each sentence carries content (cascade scope, preview, address rules, clash behavior, staging). It is dense and parenthetical-heavy, verging on run-on, which slightly hurts scannability.

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 cascading operation with no output schema, the definition covers blast radius, preview mode, redirect defaults, and error semantics. It leaves minor gaps such as required permissions and what the dryRun response actually returns, which is why it is not a 5.

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 100%, so the baseline is 3, but the description adds constraints absent from the schema: addresses must be lowercase words with dashes, nested up to 5 folder levels, and a clash is refused with a specific reason. That meaningfully supplements the loosely described path/to parameters.

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?

"Renames a folder (name) or moves it (to: a new slug or parent)" names the specific verb, resource, and the two mutually exclusive modes in the first clause, so an agent can distinguish it from move_page, move_file, or update_collection 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?

It clearly indicates the rename-vs-move selection and recommends "dryRun says what would change first" as a preview path before the destructive write. It never explicitly rules out sibling tools such as move_page for moving a single page, so the guidance is clear but not exhaustive.

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

All Xodia tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?