Skip to main content
Glama

create_wiki_page

Create a new wiki page with markdown content to store findings durably. Adds only, never overwrites existing pages.

Instructions

Write a NEW page into a wiki, with its body as markdown. This is how an agent puts findings somewhere durable instead of handing them back as chat text. wiki_uuid comes from list_wikis; parent_page_uuid (from get_wiki_tree) nests the new page under an existing one and is where a page belongs unless it is genuinely top-level. The markdown is converted server-side by the same parser ticket descriptions and comments go through — headings, lists, tables, code blocks, blockquotes, horizontal rules and links all survive. An ![alt](https://…) image survives too, as a reference to that URL — but only for a URL already hosted somewhere public, because there is no tool here to upload an attachment, and an image the reader cannot fetch renders as a broken one. Raw HTML is kept as literal text rather than interpreted, so do not reach for it to get something markdown lacks. ADD ONLY: there is deliberately no tool to change or delete what is already on a page. Wiki pages have a live collaborative editor behind them, so a whole-document overwrite from here would silently destroy whatever a person had open at the time. Adding cannot damage anything, so it is offered and overwriting is not. Do not call this twice to 'update' a page; you will get two pages — to add to a page that already exists, use append_wiki_page. Creating a page needs write access to the workspace: a read-only role or a guest key is a 403 and retrying cannot fix it. A title is required and a body is not, so a page can be created empty and filled in by a person later.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
wiki_uuidYes
content_markdownNoThe page body as markdown. Omit for an empty page. Longer than 100k characters is refused rather than truncated
parent_page_uuidNoNest under this page. Must be in the same wiki — a page from another wiki is a 400, not a silent move
Behavior5/5

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

With no annotations, the description carries the full disclosure burden and succeeds: it reveals create-only semantics, no overwrite/delete, duplicate-page behavior, server-side markdown conversion, image URL requirements, raw HTML literal handling, and permission failures. It even explains the underlying reason (collaborative editor) for not offering overwrite.

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 longer than average but every sentence adds substantive value: usage context, parameter origins, markdown behavior, mutation safety, permission notes, and requirements. It is organized into logical paragraphs and is front-loaded with the core purpose. No filler or redundant phrases.

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?

The description is exceptionally thorough for purpose, parameters, and safety, but with no output schema it does not mention what the tool returns (e.g., the new page's UUID). This is a minor gap for an agent that may need a handle for subsequent operations. Everything else needed for selection and correct invocation is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite only 50% schema description coverage, the description enriches all parameters: wiki_uuid is sourced from list_wikis, parent_page_uuid from get_wiki_tree and nests under an existing page, content_markdown receives markdown-feature details and the optionality of body, and title is confirmed required. This compensates fully for schema gaps.

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 'Write a NEW page into a wiki, with its body as markdown' – a specific verb, resource, and scope. It explicitly distinguishes itself from append_wiki_page by stating 'Do not call this twice to update a page... use append_wiki_page instead.'

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

Usage Guidelines5/5

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

Provides clear guidance on when to use: 'This is how an agent puts findings somewhere durable instead of handing them back as chat text.' It also gives explicit exclusions and alternatives: 'to add to a page that already exists, use append_wiki_page,' and warns against calling twice. Permission prerequisites (write access, 403 for read-only/guest) are stated.

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/Developyn/laver-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server