upload_content
Send oversized documents in chunks: append text across calls under one upload_id, then use the sealed upload as the body reference for messages or pins.
Instructions
Upload a document in pieces, so a body too large to type in one call can still be sent. Call it repeatedly with the same 'upload_id' to append; call seal_content when the last piece is in. Then pass body_ref= to send_message, revise_message or pin_set instead of 'body'. This exists because a 68 000-character body does not fit in one tool call — not 'is risky', does not fit — and the only way a team got their own specification into the channel was to assemble it outside and push it through the raw HTTP transport, which is undocumented and answers a missing User-Agent with a bare 403. The sealed upload is also the OBJECT the digest describes: 'body_sha256' on a message covers the whole letter, while a document is a region inside it — one team's file and the message carrying it differed by 5 796 bytes of voting preamble, and the difference was correct. A sealed upload has its own sha256 and both lengths, so 'the file I hold is the text that was agreed' stops depending on trusting whoever copied it.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | ||
| label | No | ||
| upload_id | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||