Xodia

Update a CMS collection

update_collection

Destructive

Changes a collection: settings (name, singular, plural, urlFolder, which moves the item pages with their route, the links to them and redirects for published ones, reservedSlugs, sort, manualOrder, groups, translatable and translatedOnly for the site's languages), collection page settings (page: SEO title and description templates with {field} tokens, Open Graph, canonical, noindex, JSON-LD, custom code) and fields: add, update (label, required, help, options, reference target, validation, default, translatable), rename (moves the key in every item, the page settings and code bindings of files that name the collection, in one reviewable change), reorder (every id) and delete (refused when items hold values unless allowDataLoss: ask the user first). dryRun counts what rename and delete would touch. Parts run in that order; each part that fails is listed and the rest still apply. Writes go to the branch the workspace has open as unsaved changes the user reviews and saves in Xodia, the same as the Content tab. Works on every plan within its collection and item limits (Free: 2 collections and 100 items a site); turning a folder into a Xodia collection needs a paid plan.

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": {
      "collection": "<collection>",
      "projectId": "<projectId>"
    },
    "name": "update_collection"
  }
}

Input Schema

Name	Required	Description
`page`	No	Collection page settings: titleTag and metaDescription templates with {field} tokens ("{title} \| Blog", "{summary}"; system tokens slug, createdAt, updatedAt, publishedAt, "\|date" formats a date), ogTitle and ogDescription ("sameAsSeo" or a template), ogImageField (an image field id), canonical, noindex (true or a switch field id), jsonLd {preset: article, product, event, jobPosting or custom, template}, customCode {head, bodyEnd} with tokens (values HTML-escaped). Replaces the whole page object; null clears it
`branch`	No	Optional branch; default the branch the workspace has open
`dryRun`	No	Only count what rename and delete would change; writes nothing
`fields`	No
`settings`	No
`projectId`	Yes	Project id from list_projects
`collection`	Yes	The collection id (its folder under content/), from list_collections
`allowDataLoss`	No	Deleting a field that items have values in is refused unless this is true. Ask the user first

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.1/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 adds what they cannot: parts execute in a fixed order, failures are reported per part while the rest still apply, and writes land on the open branch as unsaved changes the user reviews and saves. It also states data-loss refusal, dryRun semantics, and plan limits (Free: 2 collections, 100 items; folder-to-collection needs a paid plan).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The entire definition is one ~1,400-character run-on sentence with deep nested parentheses, so the field operations, page settings, ordering rules, branch behavior, and plan limits all blur together. The content is largely load-bearing, but it is not front-loaded beyond the opening clause and a bulleted or multi-sentence structure would make it far more usable.

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 an 8-parameter, deeply nested destructive mutation with no output schema, it covers partial-failure behavior, dry-run scope, data-loss guardrails, branch targeting, and plan limits. It leaves out what the call returns (no output schema exists to compensate) and any permission/auth requirements, which are the remaining gaps.

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 75% with unusually rich per-property descriptions (urlFolder routing/redirects, reservedSlugs, sort, allowDataLoss), so the baseline is 3. The description re-enumerates those same settings rather than adding much new meaning, though 'Parts run in that order' and the dryRun scoping do clarify cross-parameter interaction that the schema cannot express.

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?

Names a specific verb (changes) and resource (a collection) and then enumerates the three sub-surfaces it mutates: settings, page settings, and fields with add/update/rename/reorder/delete operations. Clear enough to separate it from create_collection, update_folder, and update_item 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?

Gives real decision rules: delete is refused when items hold values unless allowDataLoss, and the user must be asked first; dryRun is scoped to rename and delete; translatable should be flipped 'Only when the user asks'. It never names a sibling alternative (create_collection vs. turning a folder into a collection is only implied by the plan note), so it stops short of full when/when-not routing.

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?