Share notebook text (opens a draft)
notebook_shareBuild a RelayLink package from chosen notebook entries and open it as a draft to one of the user's contacts. The recipient receives only the entries named and the covering note — never the notebook itself, the revision history, the journal, the working preferences or anything else in the project. NOTHING IS SENT: this returns a preview for the user to approve or rewrite, and confirm_send after their explicit approval is what delivers it, with every ordinary rule — accepted contact, blocks, the sacred human note — applying unchanged. Which entries and which revisions went is recorded, so a later private edit cannot change what somebody already received. There is no length to keep to: a short selection travels as the package's briefing and a long one as its message, so an entry of any size the notebook accepts can be sent as written — whoami says the longest message this account's plan allows, and only a selection past THAT is refused, with the number. Never shorten the user's own writing to make it fit. One exception worth knowing before a first approach: a first message to somebody who has no account yet must be a briefing, so a long share needs an existing contact. This is the user's RelayLink notebook, for material they are keeping: use it when they name RelayLink or their notebook, when they are continuing work already kept here, or when they pick a RelayLink entry. A durable fact ABOUT them — how they like to be worked with, what they are working on — is memory_add's instead, and a project-scoped preference or one with an end date is this notebook's. A bare "add a task" or "save this note" may be meant for another connected app, and a destination they name outright is always the destination. If more than one place is plausible and nothing settles it, ask once, then stay with the answer for the rest of the task.
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": {
"entryIds": "<entryIds>",
"to": "<to>",
"note": "<note>",
"ask": "<ask>"
},
"name": "notebook_share"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | The recipient's email address, or the name of an accepted contact resolved by draft_package's rules. | |
| ask | Yes | What the sender wants back, one sentence. | |
| note | Yes | The sender's own words to the recipient, at most 2000 characters. A proposal — the user must approve or rewrite it before anything is sent. | |
| topic | No | A few words naming the thread. Defaults to the first entry's title. | |
| urgency | No | Urgency hint: none | when_convenient | this_week | today. | when_convenient |
| entryIds | Yes | The entry_ids to include, at most 8. Their current text goes into the briefing. | |
| responseShape | No | Shape of the wanted response: opinion | decision | review | info | fyi. | opinion |