Skip to main content
Glama

write_edit_text

Replace one exact passage in a page using its ID and current version, without rewriting the whole page. Use an empty replacement to remove the passage.

Instructions

Replace one exact passage of a page's content, without sending the whole page.

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>",
      "find": "<find>",
      "replace": "<replace>"
    },
    "name": "write_edit_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
findYesExact text, occurring once in the page
pageYesPage id or path
replaceYesNew text; empty removes the passage
versionYesversion from your last read of the page

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 destructiveHint=false and openWorldHint=false, so safety basics are covered; the description adds that the edit is scoped to a single occurrence rather than a full document rewrite. It does not disclose failure behavior when the passage is missing or appears multiple times, nor the version-conflict semantics implied by the required version parameter.

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 key constraint (surgical replacement vs. whole-page write) stated immediately; no filler and nothing the reader must re-read.

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?

Adequate for a 4-parameter mutation with full schema coverage and no output schema, but it omits what happens on version mismatch or non-unique match, which is exactly the information an agent needs to call it reliably in a concurrent editing environment.

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 100%, so every parameter (page, version, find, replace) is already documented in the schema, including that empty replace removes the passage. The description adds no parameter-level meaning beyond that, making the baseline 3 appropriate.

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?

Specific verb ("Replace") plus a precisely bounded resource ("one exact passage of a page's content"), and the clause "without sending the whole page" implicitly distinguishes it from whole-page update tools. It stops short of naming the sibling it differs from, so an agent must infer that write_update_page (or similar) is the alternative.

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?

Usage context is only implied: the phrase "without sending the whole page" suggests this is the preferred tool for small, surgical edits, but it never says when to prefer a whole-page update, nor does it state prerequisites such as needing a fresh version from a prior read.

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