Skip to main content
Glama

wikijs_create_page

Create a new wiki page by specifying path, title, and content. Supports rich markdown including callouts, tabs, diagrams, and custom CSS/JS. Requires mutations enabled.

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?

With no annotations, the description must disclose behavioral traits. It adds context about the 'confirm' parameter being conditional on WIKI_MUTATION_CONFIRM_TOKEN, which is helpful. However, it lacks details on mutation safety, idempotency, or side effects, leaving significant behavioral gaps.

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 consists of two concise sentences with no redundant information. It is front-loaded with the core purpose and then a critical requirement and parameter behavior, which is efficient for an agent to parse.

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?

Despite the high schema coverage, the description fails to provide a complete picture for a tool with 14 parameters and no output schema. It omits information on return values, error handling, and guidance on optional parameters. The minimal description does not adequately support the tool's complexity.

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 only a small extra semantic for the 'confirm' parameter. The rest of the parameters are not elaborated beyond the schema, thus meeting the baseline without significant added value.

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' with a specific verb and resource. It distinguishes itself from sibling tools like wikijs_create_comment or wikijs_update_page, leaving no ambiguity about the tool's purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description mentions a prerequisite (WIKI_MUTATIONS_ENABLED=true) but provides no explicit guidance on when to use this tool versus alternatives like wikijs_update_page. No reasoning for selecting this tool over siblings is given.

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