Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Create Wiki page

wiki_pages_create

Creates a new wiki page at a specified slug, returning its numeric ID for subsequent operations. Choose the slug carefully as it becomes permanent.

Instructions

Create a wiki page at body.slug (POST /pages).

Treat the slug as permanent: pages_move can rename the page later, but the old address then answers 404 and links to it break, so pick the slug carefully. Returns the created page (its numeric id drives the id-based tools and every subsequent write). E.g. {"body": {"slug": "data/x", "title": "X", "content": "# X"}}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesTyped request body for ``POST /pages``: a new page at ``slug``.
fieldsNoExtra blocks to include in the reply (CSV), e.g. ``content,attributes``.
is_silentNoDo not notify the page's subscribers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.122.1
    • addedInput schema / properties / body
      Added value: +{
+  "additionalProperties": false,
+  "description": "Typed request body for ``POST /pages``: a new page at ``slug``.",
+  "properties": {
+    "access_policy": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "description": "Who may open a page, in a create or update body (``access_policy``).",
+          "properties": {
+            "access_type": {
+              "anyOf": [
+                {
+                  "enum": [
+                    "inherited",
+                    "all_staff",
+                    "custom"
+                  ],
+                  "type": "string"
+                },
+                {
+                  "type": "string"
+                }
+              ],
+              "description": "``inherited`` (as the parent), ``all_staff`` or ``custom``."
+            },
+            "all_staff_role": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ],
+              "default": null,
+              "description": "Role every employee gets under ``all_staff``, e.g. editor."
+            }
+          },
+          "required": [
+            "access_type"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Who may open the page."
+    },
+    "content": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Body of the page in YFM markdown."
+    },
+    "slug": {
+      "description": "Address of the page, e.g. ``data/x``.",
+      "type": "string"
+    },
+    "title": {
+      "description": "Title of the page.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "slug",
+    "title"
+  ],
+  "type": "object"
+}
    • removedInput schema / properties / content
      Removed value: -{
-  "description": "Page body in YFM markdown.",
-  "type": "string"
-}
    • addedInput schema / properties / is_silent / anyOf
      Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / is_silent / default
      Previous value: -falseNew value: +null
    • removedInput schema / properties / is_silent / type
      Removed value: -"boolean"
    • removedInput schema / properties / slug
      Removed value: -{
-  "description": "Target slug, e.g. ``data/x``. Treat it as permanent (a move breaks links).",
-  "type": "string"
-}
    • removedInput schema / properties / title
      Removed value: -{
-  "description": "Page title.",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "slug",
-  "title",
-  "content"
-]New value: +[
+  "body"
+]
  2. First observedv0.67.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare non-readonly, non-idempotent, non-destructive, and open-world. The description adds non-obvious behavior beyond that: the 404-after-move consequence, slug permanence, and that the created page (with its numeric id) is returned and drives subsequent writes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and endpoint, and each following sentence earns its place (slug caution, rename semantics, return value, example). The double-backtick formatting makes it slightly denser than needed but nothing is wasted.

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?

With no output schema, explaining that the created page and its id come back is important, and the example covers the nested body. The optional fields (content, access_policy, is_silent) are left to the schema, which documents them fully, so the gap is minor.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine value by tying body.slug to the concept of a permanent address and supplying a concrete nested-body example for a tool whose primary parameter is a nested object.

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?

States a specific verb and resource ('Create a wiki page at body.slug') with the backing endpoint, and is clearly distinguishable from siblings like wiki_pages_update, wiki_pages_move, and wiki_pages_clone.

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?

Gives real decision context: pick the slug carefully because it is effectively permanent, and names pages_move as the later-rename path that breaks links. It stops short of stating explicit when-not-to-use conditions versus clone/append.

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