Skip to main content
Glama

Write page

wiki_write
Destructive

Create a page, or replace its title, whole Markdown content, or whole metadata. Omitted fields are preserved on existing pages. Read an existing page first and supply its revision. To change part of a page, use wiki_edit. The result's problems name the links in it that point at nothing; fix them unless the page they name is about to be written.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>",
      "org": "<org>"
    },
    "name": "wiki_write"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYesslug of the organization whose wiki to use. Required on every call, even when only one organization is listed; a path never names it.
pathYesThe wiki's name, a colon, then the page's dot-separated path (general:docs.deploy).
titleNoUse null to clear the title.
contentNoThe complete Markdown body, not a patch.
messageNoA brief note on the change describing the change.
metadataNoReplace all metadata; use wiki_updateMeta to merge properties instead.
ifRevisionNoThe revision returned by wiki_read; omit when creating a page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description goes further: omitted fields are preserved on existing pages (so partial calls are safe in that respect), a revision must be supplied for existing pages, and the response carries 'problems' naming broken links with guidance on handling them. That is real behavioral context beyond the structured fields.

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 create/replace semantics, then prerequisites, then the sibling pointer, then return-value handling — three tight sentences with no filler. The final sentence about 'problems' is slightly tangled in its phrasing but still pays for itself.

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 destructive, seven-parameter mutation with no output schema, the definition covers the key risks: preservation of omitted fields, revision requirements, and post-write link problems. It does not say what happens if the target page already exists versus not, a small gap for a tool that both creates and replaces.

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; the description earns extra credit by stating that omitted fields are preserved and that the revision comes from wiki_read, which explains the optionality semantics of title/content/metadata across create vs. replace. It does not restate the merge-vs-replace rule for metadata, which the schema already covers.

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 page') plus the exact replacement scope (title, whole Markdown content, whole metadata), and explicitly distinguishes itself from 'wiki_edit' for partial changes. An agent can tell what this tool does and what it does not do without opening the schema.

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?

Gives an explicit prerequisite ('Read an existing page first and supply its revision') and names the alternative for the adjacent use case ('To change part of a page, use wiki_edit'). When-to-use and when-not-to-use are both covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources