Skip to main content
Glama

Edit page

wiki_edit
Destructive

Change part of a page: replace one exact string in its content and leave the rest as it is. oldString must occur exactly once, with enough of the surrounding text to make it unique, unless replaceAll is set. Prefer this to wiki_write for any change smaller than the whole page. The result's problems name the links on the page 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>",
      "oldString": "<oldString>",
      "newString": "<newString>",
      "org": "<org>"
    },
    "name": "wiki_edit"
  }
}

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).
messageNoA brief note on the change.
newStringYesThe text to put in its place.
oldStringYesThe exact text to replace, copied from the page as read.
ifRevisionNoThe revision returned by wiki_read.
replaceAllNoReplace every occurrence.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare a destructive, non-read-only mutation, and the description adds substantive behavior beyond that: the oldString must match exactly once unless replaceAll is set, and the result surfaces dangling-link 'problems' with advice on handling them. It does not discuss revision staleness or what a partial failure looks like, which keeps it from a 5.

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?

Three short sentences with the core action front-loaded, the uniqueness rule second, and the sibling routing third. The closing sentence about the result's 'problems' is slightly compressed and takes a second read, but no sentence is filler.

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, the description usefully characterizes the returned problems as dangling-link reports and tells the agent what to do about them. Concurrency behavior around ifRevision is left entirely to the schema, which is the main residual gap for a mutation tool of this complexity.

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 baseline would be 3, but the description adds meaning the schema does not carry: oldString must be a unique occurrence with enough surrounding context, and replaceAll lifts that constraint. The remaining parameters (path, org, message, ifRevision, newString) are explained only by the schema.

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 ('Change part of a page'), then narrows scope precisely: replace one exact string, leave the rest untouched. It explicitly contrasts with wiki_write for whole-page changes, so an agent can pick between the two without opening either 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?

Names the alternative (wiki_write) and the exact condition that selects it ('any change smaller than the whole page'). It also gives follow-up guidance on broken links reported in the result and the exception case where they should be ignored, which is real when-to-act guidance rather than a restatement.

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