Skip to main content
Glama
ni-c

wikijs-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Move or rename a page

move_page
Idempotent

Move a Wiki.js page to a different path or locale. Since internal links aren't rewritten, review them beforehand to avoid broken links.

Instructions

Moves a page to another path, another locale, or both. Internal links pointing at the old path are NOT rewritten by Wiki.js — check list_page_links first if that matters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoPage path without a leading slash and without the locale prefix, e.g. "docs/setup". A browser URL looks like /en/docs/setup — drop the "en/", it is the locale argument. (Not enforced: "ci/", "db/" and "qa/" are perfectly good first segments that happen to look like locale codes.)
localeNoLocale code. Defaults to WIKIJS_LOCALE. The locale is part of a page’s identity.
page_idNoNumeric Wiki.js id.
confirm_tokenNoToken from this tool’s previous, unconfirmed call. Omit it to receive one.
destination_pathYesPage path without a leading slash and without the locale prefix, e.g. "docs/setup". A browser URL looks like /en/docs/setup — drop the "en/", it is the locale argument. (Not enforced: "ci/", "db/" and "qa/" are perfectly good first segments that happen to look like locale codes.)
destination_localeNoLocale code. Defaults to WIKIJS_LOCALE. The locale is part of a page’s identity.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
truncatedNoPresent only when the answer was shortened to fit the budget.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • changedInput schema / properties / page_id / maximum
      Previous value: -9007199254740991New value: +2147483647
  2. Changed2 schema fields changedv0.2.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": true,
+  "properties": {
+    "truncated": {
+      "additionalProperties": true,
+      "description": "Present only when the answer was shortened to fit the budget.",
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  3. First observedv0.1.2

TDQS

A4.1/5.0
Behavior4/5

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

The description discloses a key behavioral trait beyond the annotations: internal links are not rewritten, a side effect an agent must know before invoking. Since readOnlyHint, destructiveHint, and idempotentHint already cover the safety profile, the added link-rewriting caveat is genuine value. It does not mention the two-phase confirm-token flow, though that is documented in the confirm_token parameter description.

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?

Two sentences with zero filler: the action is front-loaded in sentence one, and the critical caveat follows immediately in sentence two. Every clause earns its place, and the warning is positioned where the agent will see it before acting.

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

Completeness3/5

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

The description covers the core action and the most important caveat, and the output schema plus 100% param coverage carry the rest. However, there is a real gap: only destination_path is required, yet the description never explains how the source page is identified (path and locale vs page_id), which could lead an agent to invoke the tool with only a destination. The confirm-token two-step flow is also only discoverable in the schema, not flagged in the description.

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 description coverage is 100%, so the baseline is 3. The phrase "another path, another locale, or both" adds mild combination semantics for destination_path and destination_locale, but the description contributes no format, precedence, or identification details beyond what the schema already documents.

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 states a specific verb and resource: "Moves a page to another path, another locale, or both." It clearly delimits the operation's scope and distinguishes it from sibling tools like update_page (content editing), delete_page, and migrate_pages_locale (bulk locale migration). An agent can tell what this tool does and what it does not do.

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 gives explicit actionable guidance: "Internal links pointing at the old path are NOT rewritten by Wiki.js — check list_page_links first if that matters," naming the exact alternative tool and the condition that selects it. However, it offers no routing guidance versus other page-handling siblings (update_page, migrate_pages_locale), so exclusions are not comprehensive.

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

Deploy Server

Other Tools