create_page
Propose a new page in a Plainwork collection. Queued for approval by default.
Last updated
create_page
Propose a new page in a Plainwork collection. Unless the agent has auto-approve enabled, the proposal is queued for a human to approve, edit, or reject before the page is actually created.
Arguments
| Name | Type | Required | Description |
|---|---|---|---|
collection_id | string | yes | ID of the target collection. Discover via list_collections. |
title | string | yes | Title of the new page. Maximum 500 characters. |
body | string | no | Markdown body content. |
tags | string[] | no | Tags to attach. |
folder_id | string | no | Optional folder within the collection. |
Returns
When auto-approve is off (the default)
{
"content": [
{
"type": "text",
"text": "Proposal submitted — awaiting approval in Plainwork before the page is created. Action ID: act_abc123. The user can approve, reject, or edit it first."
}
]
}
When auto-approve is on
{
"content": [
{
"type": "text",
"text": "Page created: \"Standup 2026-04-10\" (id: note_xyz789)."
}
]
}
In both cases the response is a single text block. The Action ID: … or
id: … token lets the agent reference the proposal or the page in a
follow-up message.
Example
{
"tool": "create_page",
"arguments": {
"collection_id": "col_a1b2c3",
"title": "Standup 2026-04-10",
"body": "## Attendees\n- Alice\n- Bob\n\n## Notes\n- Shipped MCP docs",
"tags": ["standup"]
}
}