Skip to main content
Glama

write_update_page

Update a LeafWiki page's title, slug, Markdown content, tags or properties; omitted fields stay unchanged and version checks prevent overwriting others' edits.

Instructions

Change a page's title, slug, content, tags or properties; fields you leave out stay as they are.

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": {
      "page": "<page>",
      "version": "<version>"
    },
    "name": "write_update_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesPage id or path
slugNoNew URL segment; changes the path, which can break links
tagsNoFull tag list, replaces the current one
titleNo
contentNoFull new Markdown content
versionYesversion from your last read of the page
propertiesNoFull property map, replaces the current one

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare openWorldHint=false and destructiveHint=false, and the description usefully adds merge semantics that the hints do not cover. However, it stays silent on the version/concurrency behavior (a stale version presumably causes a conflict) and on the fact that a slug change breaks links, both of which are the real risks of this call.

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?

A single front-loaded sentence with the editable fields first and the partial-update rule second; no filler or redundancy.

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

Completeness3/5

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

For a seven-parameter mutation with a nested property map and a required version token, the description covers what can be changed but not the failure modes an agent must plan around, notably version-conflict rejection. Without an output schema the description would need to say more about the result of a successful write.

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 86%, so the schema already explains page identifiers, slug path changes, and full replacement of tags and properties. The description only restates the field list and adds the omission-means-unchanged rule, which is marginal value over the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource plus the exact set of editable fields ('title, slug, content, tags or properties'), which separates it from narrower siblings like write_properties or write_tags. It never names an alternative tool, so the differentiation is inferred from field coverage rather than stated.

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 phrase 'fields you leave out stay as they are' implies this is the partial-update path for existing pages, which is useful usage context. There is no explicit when-not guidance and no pointer to siblings such as write_edit_text or write_move for narrower operations.

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