Skip to main content
Glama

Patch page section

patch_page

Edit a single section of a wiki page without rewriting the entire document. Use a heading path to target the section and apply append, prepend, replace, or delete operations.

Instructions

Surgically edit ONE section of a page instead of rewriting the whole body (editor+). First call get_page format:"map" to see the section paths, then patch the target. Cheaper and safer than update_page on a long page — it never touches the rest of the document. Snapshots a revision like any edit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYespage id to patch
targetYesthe section to edit, by its heading path from get_page format:"map" (e.g. 'Setup' or 'Deploy > Production'); the bare heading text also resolves
contentNomarkdown to insert; omit for delete
operationYesappend (add to the end of the section's body), prepend (add right under the heading), replace (swap the section's body, heading kept), or delete (remove the heading and its body)
idempotency_keyNooptional client-generated key; a retry with the same key returns the original result instead of re-applying the patch

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYes
Behavior5/5

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

The description goes beyond annotations by stating 'never touches the rest of the document' and 'snapshots a revision like any edit.' Since annotations declare readOnlyHint=false and destructiveHint=false, the description adds valuable context about safety and revision behavior without contradiction.

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?

Two sentences that are dense with information: first sentence states purpose and comparison, second provides workflow step and safety reassurance. No unnecessary words, front-loaded with key action.

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

Completeness5/5

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

Given the presence of an output schema, the description covers all needed context: when to use, prerequisites, behavioral traits, and parameter details. It is fully adequate for an agent to select and invoke the tool correctly.

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?

Schema coverage is 100%, but the description adds meaning: it explains how 'target' works (heading path from get_page map), describes operations (append, prepend, replace, delete), and clarifies content usage ('markdown to insert; omit for delete'). This enriches parameter understanding.

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 clearly states the tool's purpose: 'Surgically edit ONE section of a page instead of rewriting the whole body.' The verb 'surgically edit' and resource 'page section' are specific, and it distinguishes from sibling tool 'update_page' by emphasizing that it only edits one section.

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?

Explicit guidance is provided: 'First call get_page format:"map" to see the section paths,' and it compares to update_page: 'cheaper and safer than update_page on a long page — it never touches the rest of the document.' This tells the agent when and how to use the tool.

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/zcag/tela'

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