Radix Wiki

Edit a page

edit_page

Destructive

Edit an existing Radix Wiki page. Requires a ROLA bearer token; see https://radix.wiki/AGENTS.md. Read the page with get_page and blocks: true, send the full revised block array, and pass its version as baseVersion: an edit made after someone else's is refused rather than written over it, so read again and reapply. The version bump, block-level diff, and revision entry are computed server-side. Needs a wallet holding at least 20,000 $XRD (ideas 10,000). Locked and author-only pages are rejected. Earns contribution points.

Input Schema

Name	Required	Description
`slug`	Yes	Slug of the page to edit
`title`	No	New title
`content`	No	The full revised block array (not a patch). Omit to change only the title or metadata.
`newSlug`	No	Move the page to this slug (an article only)
`tagPath`	Yes	Tag path of the page to edit
`metadata`	No	Replacement metadata object: the whole `metadata` get_page returns with `blocks: true`, revised
`verified`	No	True when you checked the page's facts against its sources: stamps lastVerifiedAt. Send it alone to stamp without an edit.
`editorIds`	No	User ids who may co-edit an author-only page. Applied only when the author sends it.
`bannerImage`	No	Banner image URL; an empty string removes it
`baseVersion`	Yes	The `version` get_page returned, which this edit starts from
`revisionMessage`	No	What changed and why — shown in the page history. Always send one.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

changedInput schema / properties / content / items / properties / metric / enum

Previous value: -[
-  "transactions",
-  "activeAccounts",
-  "newAccounts",
-  "newComponents",
-  "newResources",
-  "nftsMinted",
-  "feesXrd",
-  "burnedXrd",
-  "royaltiesXrd"
-]New value: +[
+  "transactions",
+  "activeAccounts",
+  "newAccounts",
+  "newComponents",
+  "newResources",
+  "nftsMinted",
+  "feesXrd",
+  "royaltiesXrd"
+]

Changed2 schema fields changedOct 24, 2026

changedInput schema / properties / content / items / description

Previous value: -"A typed block with a unique `id` (UUID) and a `type`. A `content` block carries semantic HTML in `text`; an `infobox` carries nested `blocks`. For any other type, copy the shape of one already on a page: get_page with `blocks: true` (or GET /api/wiki/{path}) returns blocks as stored."New value: +"A typed block with a unique `id` (UUID) and a `type`. A `content` block carries semantic HTML in `text`; an `infobox` carries nested `blocks`. An `events` block carries `items: [{ id, date, end?, text }]`, each date a year, month or day (`2026`, `2026-11`, `2026-11-12`) and `text` inline HTML saying what and where, in any order: the page sorts them into upcoming and past by the day it is read. A `locations` block carries `items: [{ id, name?, address?, map?, phone?, email?, hours?, timeZone?, note? }]`, each with its address (plain text, a line to a line) or its `hours`, rows of `{ days: [\"mon\"…\"sun\"], opens: \"08:00\", closes: \"18:00\" }`; the page groups the days and says whether each place is open by its own clock. For any other type, copy the shape of one already on a page: get_page with `blocks: true` (or GET /api/wiki/{path}) returns blocks as stored."

changedInput schema / properties / content / items / properties / type / enum

Previous value: -[
-  "content",
-  "banner",
-  "columns",
-  "list",
-  "assetPrice",
-  "networkChart",
-  "rssFeed",
-  "codeTabs",
-  "linkGrid",
-  "tipJar",
-  "references",
-  "infobox",
-  "stats",
-  "testimonial"
-]New value: +[
+  "content",
+  "banner",
+  "columns",
+  "list",
+  "assetPrice",
+  "networkChart",
+  "rssFeed",
+  "codeTabs",
+  "linkGrid",
+  "tipJar",
+  "references",
+  "locations",
+  "events",
+  "infobox",
+  "stats",
+  "testimonial"
+]

Changed7 schema fields changedOct 21, 2026

addedInput schema / properties / content / items / properties / count

Added value: +{
+  "description": "How many of the newest (list)",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

removedInput schema / properties / content / items / properties / pageIds

Removed value: -{
-  "description": "Page ids in display order (pageList): the `id` get_page returns with `blocks: true`",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

addedInput schema / properties / content / items / properties / pages

Added value: +{
+  "description": "Page ids in display order (list, `chosen`): the `id` get_page returns with `blocks: true`",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 100,
+  "type": "array"
+}

addedInput schema / properties / content / items / properties / show

Added value: +{
+  "description": "Each page as a link with its age, or as a card with its banner and opening line (list)",
+  "enum": [
+    "links",
+    "cards"
+  ],
+  "type": "string"
+}

addedInput schema / properties / content / items / properties / source

Added value: +{
+  "description": "Where a list's pages come from (list): `under` the pages in the category `under` names, `newest` the newest `count` pages (within `under` if given), `chosen` the pages in `pages`",
+  "enum": [
+    "under",
+    "newest",
+    "chosen"
+  ],
+  "type": "string"
+}

changedInput schema / properties / content / items / properties / type / enum

Previous value: -[
-  "content",
-  "banner",
-  "columns",
-  "recentPages",
-  "pageList",
-  "assetPrice",
-  "networkChart",
-  "rssFeed",
-  "codeTabs",
-  "linkGrid",
-  "tipJar",
-  "references",
-  "infobox",
-  "stats",
-  "testimonial"
-]New value: +[
+  "content",
+  "banner",
+  "columns",
+  "list",
+  "assetPrice",
+  "networkChart",
+  "rssFeed",
+  "codeTabs",
+  "linkGrid",
+  "tipJar",
+  "references",
+  "infobox",
+  "stats",
+  "testimonial"
+]

addedInput schema / properties / content / items / properties / under

Added value: +{
+  "description": "A tag path, such as `contents/tech` (list)",
+  "type": "string"
+}

Changed10 schema fields changedOct 20, 2026

addedInput schema / properties / bannerImage

Added value: +{
+  "description": "Banner image URL; an empty string removes it",
+  "type": "string"
+}

addedInput schema / properties / baseVersion

Added value: +{
+  "description": "The `version` get_page returned, which this edit starts from",
+  "type": "string"
+}

addedInput schema / properties / content / items / additionalProperties
```
Added value: +true
```

addedInput schema / properties / content / items / description

Added value: +"A typed block with a unique `id` (UUID) and a `type`. A `content` block carries semantic HTML in `text`; an `infobox` carries nested `blocks`. For any other type, copy the shape of one already on a page: get_page with `blocks: true` (or GET /api/wiki/{path}) returns blocks as stored."

addedInput schema / properties / content / items / properties

Added value: +{
+  "blocks": {
+    "description": "Nested leaf blocks (infobox)",
+    "items": {
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "id": {
+    "format": "uuid",
+    "type": "string"
+  },
+  "metric": {
+    "description": "The series charted (networkChart)",
+    "enum": [
+      "transactions",
+      "activeAccounts",
+      "newAccounts",
+      "newComponents",
+      "newResources",
+      "nftsMinted",
+      "feesXrd",
+      "burnedXrd",
+      "royaltiesXrd"
+    ],
+    "type": "string"
+  },
+  "pageIds": {
+    "description": "Page ids in display order (pageList): the `id` get_page returns with `blocks: true`",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "text": {
+    "description": "Semantic HTML (content, banner)",
+    "type": "string"
+  },
+  "type": {
+    "enum": [
+      "content",
+      "banner",
+      "columns",
+      "recentPages",
+      "pageList",
+      "assetPrice",
+      "networkChart",
+      "rssFeed",
+      "codeTabs",
+      "linkGrid",
+      "tipJar",
+      "references",
+      "infobox",
+      "stats",
+      "testimonial"
+    ],
+    "type": "string"
+  }
+}

addedInput schema / properties / content / items / required
```
Added value: +[
+  "id",
+  "type"
+]
```

addedInput schema / properties / editorIds

Added value: +{
+  "description": "User ids who may co-edit an author-only page. Applied only when the author sends it.",
+  "type": "array"
+}

changedInput schema / properties / metadata / description

Previous value: -"Replacement metadata object"New value: +"Replacement metadata object: the whole `metadata` get_page returns with `blocks: true`, revised"

addedInput schema / properties / newSlug

Added value: +{
+  "description": "Move the page to this slug (an article only)",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "tagPath",
-  "slug"
-]New value: +[
+  "tagPath",
+  "slug",
+  "baseVersion"
+]

Changed1 schema field changedOct 15, 2026

addedInput schema / properties / verified

Added value: +{
+  "description": "True when you checked the page's facts against its sources: stamps lastVerifiedAt. Send it alone to stamp without an edit.",
+  "type": "boolean"
+}

First observedAug 2, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations, it discloses authentication requirements, wallet balance prerequisites, optimistic concurrency behavior, server-side computation of version/diff/revision, page restrictions, and contribution points. These details materially improve safe invocation. The destructiveHint annotation is consistent with replacing the full block array.

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?

The description is a dense but front-loaded paragraph: purpose first, then prerequisites, workflow, conflict behavior, restrictions, and side effects. For an 11-parameter mutation tool, every sentence contributes relevant context without padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

It covers the full complexity of the tool: auth, wallet requirements, read-before-edit workflow, concurrency refusal, server-side effects, rejected page states, and contribution-point side effects. No output schema is present, but the description does not need to explain return values and otherwise leaves no major operational gap.

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 schema already carries most parameter meaning. The description adds useful workflow semantics around `baseVersion` conflict handling and full-array replacement, though several parameter explanations overlap with existing schema descriptions.

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?

The description opens with a specific verb and resource: editing an existing Radix Wiki page. It clearly distinguishes this from reading via get_page and implies the lifecycle distinction from create_page/delete_page, so an agent can identify the tool 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit operational guidance: read the page first with get_page and `blocks: true`, send the full revised block array, and pass `version` as `baseVersion`. It also states when the edit is refused, what to do on conflict, and that locked or author-only pages are rejected.

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

All Radix Wiki tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?