Skip to main content
Glama

wikijs_create_page

Create a new Wiki.js page by providing path, title, and markdown content. Supports rich formatting: callouts, tabs, diagrams, custom CSS/JS.

Instructions

Create a new page. 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.
pathYesTarget page path.
titleYesPage title.
contentYesPage 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.
descriptionNoShort page description.
localeNoLocale code.
editorNoEditor key (markdown, asciidoc, html, etc).
tagsNoOptional string tags.
isPublishedNoDefaults true.
isPrivateNoDefaults false.
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.
Behavior2/5

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

No annotations are provided, so the description fully bears the burden of behavioral disclosure. It mentions the required environment variable and confirm token behavior but lacks details on success/error responses, side effects, or permissions. This is insufficient for a mutation tool with 14 parameters.

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 extremely concise with two sentences, no redundant wording, and no unnecessary details. Every sentence adds value.

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 14 parameters and no output schema, the description is too sparse. It lacks information about return values, error handling, prerequisites beyond the environment variable, or workflow integration. A more comprehensive description would aid the agent significantly.

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 100%, so the baseline is 3. The description adds context for the confirm parameter's conditional validation but does not elaborate on other parameters, which are already well-documented in the schema. Minimal added value beyond 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?

The description clearly states 'Create a new page,' which is a specific verb and resource. It distinguishes itself from sibling tools like wikijs_delete_page and wikijs_update_page by focusing on creation.

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?

The description provides a key prerequisite: 'Requires WIKI_MUTATIONS_ENABLED=true.' and explains the confirm parameter's dependency on WIKI_MUTATION_CONFIRM_TOKEN. However, it does not explicitly guide when to use this over alternative tools like wikijs_update_page for modifications.

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/Lil-Beast-666/wikijs-mcp-http'

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