Atwork

Edit Page

page.edit

Destructive

Patch an existing page with one of five targeted operations. append/prepend add markdown at end/start. append-to-section inserts at the end of a section (before the next heading) — use this when adding to a section, NOT replace-section. replace-section swaps a section's heading + body with new markdown; drops any non-text blocks (images/files) inside it. delete-section removes a section entirely. sectionHeading matches case-insensitive trim. Always call page.read FIRST so you know the actual heading text. The page changes immediately; the user has 30 seconds to undo.

Input Schema

Name	Required	Description	Default
`op`	Yes
`pageId`	Yes
`markdown`	No
`sectionHeading`	No

Output Schema

Name	Required	Description
`op`	Yes	The operation that ran
`name`	Yes	Page name
`pageId`	Yes	Id of the edited page
`spaceId`	Yes	Space the page is in
`previousContent`	Yes	The replaced or removed blocks (BlockNote JSON) for undo, or null
`previousContentTooLarge`	Yes	True when previousContent was omitted for size

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 4, 2026

removedOutput schema / properties / name / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / name / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / spaceId / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / spaceId / type
```
Added value: +[
+  "number",
+  "null"
+]
```

Changed2 schema fields changedOct 27, 2026

addedOutput schema / properties / spaceId

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Space the page is in"
+}

changedOutput schema / required

Previous value: -[
-  "pageId",
-  "name",
-  "op",
-  "previousContent",
-  "previousContentTooLarge"
-]New value: +[
+  "pageId",
+  "name",
+  "spaceId",
+  "op",
+  "previousContent",
+  "previousContentTooLarge"
+]

First observedOct 20, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the annotations (destructive, non-idempotent), the description discloses the critical side effects: edits apply immediately with only a 30-second undo window, and replace-section silently drops non-text blocks such as images and files. It also explains that sectionHeading matching is case-insensitive after trimming, which is behavior an agent cannot infer from the annotations.

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?

The content is front-loaded and dense with useful detail, and each operation is covered without fluff. The em-dash-heavy construction and the repeated 'section' clauses make it slightly harder to scan, but no sentence is wasted.

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?

An output schema exists, so return values need not be described, and the description covers everything else an agent needs: the five operations, prerequisite reading, heading-match rules, data-loss behavior, and the undo window. Nothing required to call it correctly is missing.

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 description coverage is 0%, so the description carries the parameter burden and does so well for op values and sectionHeading matching semantics. It leaves pageId and markdown length limits unmentioned, which is a minor gap but not a blocker.

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 opens with a specific verb and resource ('Patch an existing page') and enumerates all five operations with what each does, which clearly separates it from siblings like page.update, page.delete, and page.read.

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?

It states explicit routing rules: use append-to-section rather than replace-section when adding to a section, and always call page.read first to obtain the actual heading text. The conditions that select each operation are laid out rather than left to inference.

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

All Atwork tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?