Skip to main content
Glama

wikijs_update_page

Update an existing Wiki.js page by its ID. Modify title, content, tags, or publish settings. Requires mutations to be enabled.

Instructions

Update an existing page by ID. Requires WIKI_MUTATIONS_ENABLED=true. confirm is only checked when WIKI_MUTATION_CONFIRM_TOKEN is set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoMust match WIKI_MUTATION_CONFIRM_TOKEN if set. Optional when token is not configured.
idYesPage ID to update.
titleNo
contentNoPage content in Wiki.js-flavored Markdown (when editor is "markdown"). Supports CommonMark + GFM plus Wiki.js extensions: BLOCKQUOTE STYLES — colored callout boxes: > Note text {.is-info} (blue) {.is-success} (green) {.is-warning} (yellow) {.is-danger} (red) CONTENT TABS — {.tabset} on parent heading, child headings become tabs: ## Tabs {.tabset} ### First Tab Content... ### Second Tab Content... IMAGE DIMENSIONS — append =WIDTHxHEIGHT after URL: ![alt](/img.jpg =300x200) ![alt](/img.jpg =100%x) DIAGRAMS — mermaid or plantuml fenced code blocks. For Mermaid 8.8.2 syntax details, read the wikijs://mermaid-guide resource. TABLE STYLE — {.dense} after table for compact rendering. LIST STYLES — {.grid-list} or {.links-list} after list. TEXT — ~sub~ ^super^ <kbd>Key</kbd> ~~strike~~ FOOTNOTES — [^1] inline, [^1]: definition at bottom. DECORATE — <!-- {element:.class} --> for ambiguous targets. For the full syntax reference, read the wikijs://markdown-guide resource.
descriptionNo
pathNo
localeNo
editorNo
tagsNo
isPublishedNo
isPrivateNo
publishStartDateNoPublication start date (ISO 8601 format).
publishEndDateNoPublication end date (ISO 8601 format).
scriptCssNoCustom CSS for the page. Max 10,000 chars.
scriptJsNoCustom JavaScript for the page. WARNING: executes in every visitor's browser. Only use trusted code. Max 10,000 chars.
Behavior3/5

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

No annotations are provided, so the description must bear the full burden. It discloses the mutation prerequisite and confirmation token, and includes a warning for scriptJs. However, it does not specify whether updates are partial or full replacements.

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 three concise sentences, front-loading the core purpose and prerequisites without extraneous text.

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

Completeness2/5

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

Given the tool's complexity (15 parameters, no output schema, no annotations), the description lacks details on return values, error handling, and partial update behavior, making it insufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds no new information about parameters beyond the input schema. With schema description coverage at 47%, the description should compensate but does not.

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 clearly states the verb 'Update', the resource 'existing page', and the identifier method 'by ID'. It distinguishes from create and delete options among siblings.

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 explicitly mentions prerequisites (WIKI_MUTATIONS_ENABLED=true) and confirmation token behavior, providing clear context for when to use. However, it does not compare to alternative update tools like wikijs_move_page.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/uyu423/requarks-wiki-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server