Skip to main content
Glama
ni-c

wikijs-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Flush the page cache

flush_page_cache
Idempotent

Clears the entire Wiki.js rendered-page cache, forcing pages to be re-rendered on next access. Use it to free memory or apply content updates immediately, though a busy wiki may slow temporarily.

Instructions

Drops Wiki.js’ rendered-page cache for the whole wiki. Nothing is lost, but every page has to be rendered again on first access, so a busy instance gets slower for a while.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

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. Changed3 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"
    • removedInput schema / properties / confirm_token
      Removed value: -{
-  "description": "Token from this tool’s previous, unconfirmed call. Omit it to receive one.",
-  "pattern": "^[0-9a-f]{32}$",
-  "type": "string"
-}
    • 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"
+}
  2. First observedv0.1.2

TDQS

A4.2/5.0
Behavior4/5

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

The description adds meaningful behavioral context beyond the annotations. It explicitly reassures that 'Nothing is lost,' clarifies the global scope across the entire wiki, and discloses the performance cost of re-rendering every page. It is consistent with the idempotentHint and destructiveHint=false annotations, and the readOnlyHint=false is respected since this is a mutation of the cache.

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 single tightly written sentence that leads with the action, then immediately provides the two most important consequences: nothing is lost, and performance temporarily degrades on busy instances. There is no filler or redundant restatement of the title.

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

Completeness4/5

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

For a zero-parameter, idempotent cache-flush operation with annotations covering safety and an output schema available, the description is complete enough. The only minor gap is the lack of explicit guidance about when flushing is appropriate versus alternatives, but the behavioral and performance context covers what an agent needs to make a safe call.

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?

The tool has zero parameters, so there is no parameter semantics burden on the description. The baseline for a zero-parameter tool is 4, and the description correctly states the global scope ('whole wiki') rather than implying any configurable target.

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: 'Drops Wiki.js’ rendered-page cache for the whole wiki.' This clearly distinguishes it from sibling cache-related rebuild tools like rebuild_page_tree and rebuild_search_index by specifying exactly what is flushed. The scope ('whole wiki') removes ambiguity about whether the action is targeted.

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

Usage Guidelines3/5

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

The description implies when to use the tool by explaining the consequence: every page must be rendered again on first access, with a temporary performance impact on a busy instance. However, it does not explicitly state when to choose this tool over alternatives, nor does it provide exclusions or conditions such as 'use when cached pages are stale.'

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