post_collaborator_rpc_documentId

CollabRPC is the collaborative-markup snapshot plane the Team front's editor speaks: createContent stores a document field's markup at a fresh, immutable blob ref and returns it, updateContent stores a new snapshot and answers nothing, and getContent reads back the exact snapshot a ref names.

createContent ALSO seeds the live-editing update log from the front-supplied Y.js update, so a dialog-authored description is visible in the collaborative editor — which replays that log — and not only in snapshot reads. updateContent never touches that log: peers may be live-editing the document, and their edits are not this call's to overwrite.

Every call is scoped to the caller's VERIFIED session or workspace token: the documentId's workspace must be the token's workspace when the token names one, and the caller must be a member of it. An unknown workspace, another tenant's workspace and a workspace the caller is not in all answer the same 404, so a probe learns nothing about what exists.


Tool	`post_collaborator_rpc_documentId`
Door	`https://api.hanzo.ai/v1/mcp`
Method	`tools/call` (JSON-RPC 2.0)
Arguments	3
Operation	`POST /collaborator/rpc/{documentId}`
Product	post

Arguments

Field	Type	Required	Default	Values	Description
`documentId`	`string`	—	—	—	DocumentID addresses the document field, as "<workspaceUuid>\|<objectClass>\|<objectId>\|<objectAttr>" — the collaborator-client encodeDocumentId shape, from the path.
`method`	`string`	—	—	—	Method is the verb: createContent, updateContent or getContent.
`payload`	`collabPayload`	—	—	—	Payload is the verb's argument.

tools/list declares a type and a description for each field and nothing further. A — means neither the door nor that operation constrains the field.

Object types

collabPayload is an object this tool's fields are made of, declared inside the tool's own schema and enumerated in full below.

collabPayload

Field	Type	Required	Default	Values	Description
`content`	`object`	—	—	—	Content maps a document field to its ProseMirror markup JSON.
`source`	`string`	—	—	—	Source is the blob ref a getContent reads the snapshot from. Absent means there is no snapshot to read, which answers empty content.
`updates`	`object`	—	—	—	Updates carries, per field, a base64 Y.js state update encoding the SAME markup — the front computes it (markupToYDoc → encodeStateAsUpdate) so a createContent seeds the live-editing lane's update log, not just the snapshot blob. Without it a dialog-created description is invisible in the collaborative editor, which replays the ydoc log, never the snapshot.

Call it

A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Nothing above is required, so every declared argument is shown rather than a guess at which matter.

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "post_collaborator_rpc_documentId",
         "arguments": {
           "documentId": "<documentId>",
           "method": "<method>",
           "payload": {
             "content": {},
             "source": "<source>",
             "updates": {}
           }
         }
       }
     }'

Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →

The operation behind it

Operation	Route	Product	Summary
`post_collaborator_rpc_documentId`	`POST /collaborator/rpc/{documentId}`	post	CollabRPC is the collaborative-markup snapshot plane the Team front's editor speaks:…

The same capability over plain HTTP is in the post API reference, on https://api.hanzo.ai.

All 755 tools · The door · API reference

Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).