Append to section
nodiom_appendAppends new content after the last item in a section. Changes are saved automatically.
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": {
"doc_id": "<doc_id>",
"selector": "<selector>"
},
"name": "nodiom_append"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| doc_id | Yes | Document ID. Examples: "waitlist", "content-calendar", "metrics". | |
| content | No | Same as new_content — the name the open-source nodiom-mcp server uses. | |
| selector | Yes | Structural selector. Examples: "## Signups", "## Active > li[0]", "## Active > li[contains=\"id=c_7f3a\"]". Prefer the contains form when writing: an index is a position, not an identity, so if another agent appends to the same section between your read and your write, li[0] now points at a different node and your write lands on the wrong one. A contains selector must match exactly one node or it errors rather than guessing. | |
| new_content | No | Markdown content to append. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| doc_id | Yes | The document id. | |
| appended | Yes | ||
| selector | Yes | The selector the call addressed. |