Skip to main content
Glama
ni-c

wikijs-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create an asset folder

create_asset_folder

Create a folder in the Wiki.js asset store to organize files. Set a URL slug that determines the address for all files inside the folder.

Instructions

Creates a folder in the asset store. The slug is what appears in the URL of every file inside it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoDisplay name (defaults to the slug).
slugYesURL segment for the folder.
parent_folder_idNoParent folder id. 0 (default) is the root.

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 / parent_folder_id / anyOf
      Previous value: -[
-  {
-    "description": "Numeric Wiki.js id.",
-    "maximum": 9007199254740991,
-    "minimum": 1,
-    "type": "integer"
-  },
-  {
-    "const": 0,
-    "type": "number"
-  }
-]New value: +[
+  {
+    "description": "Numeric Wiki.js id.",
+    "maximum": 2147483647,
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "const": 0,
+    "type": "number"
+  }
+]
  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

A3.8/5.0
Behavior3/5

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

The description does not contradict the annotations and reinforces that a persistent folder is created. It adds a useful behavioral note that the slug appears in the URL of every file inside the folder, which goes beyond the raw annotation hints. However, it does not mention other side effects such as uniqueness requirements, permission needs, or the impact of parent_folder_id, so it remains only minimally transparent beyond annotations.

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 two concise sentences with the primary action front-loaded and a single meaningful clarification about slug behavior. There is no redundant wording, repetition, or filler content.

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 simple create operation, the description, combined with a complete input schema, output schema, and annotations, is nearly sufficient. It clearly defines the core purpose and slug semantics. It lacks only explicit guidance about preconditions or edge cases such as whether parent folders must already exist, but most operational details are available through the structured fields.

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 parameters are already well documented. The description adds some extra meaning to the slug by explaining its URL role for files inside the folder, but it does not substantively cover name or parent_folder_id beyond what the schema already provides. This meets the baseline without adding significant new parameter insight.

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 ('creates') and resource ('folder in the asset store'), making the tool's purpose immediately clear. It also distinguishes this tool from sibling tools like list_asset_folders, upload_asset, and delete_asset by targeting the creation action on asset folders.

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 intended usage is implied—creating a folder in the asset store—but there is no explicit guidance on when to choose this over alternatives, or any mention of preconditions like checking parent folders via list_asset_folders. It provides enough context for a straightforward create operation but omits exclusion or alternative tool guidance.

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