Create meeting preparation
well_create_meeting_preparationMark meetings on the user's own calendars as prepared, after you have written their preparation, so Well does not start a separate pre-meeting check for them.
Use this tool when the user asks to prepare, brief or cover their meetings and you have written the preparation for them. Pass every meeting you covered in one call, up to 20.
REQUIRED: meetings, a list of { event_id, occurrence_start }. For one instance of a repeating meeting, pass its occurrence_start as returned by well_list_calendar_events; a single meeting takes null.
Returns { success: true, prepared, already_prepared, refused } where refused lists event ids that a scheduled run did not cover. A call naming a meeting that is not on the user's own calendars fails as a whole and marks nothing.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| meetings | Yes | ||
| workspace_id | No | Target workspace. Omit when the token authorizes one workspace. Required when it authorizes several — a write lands in exactly one workspace and this call would not say which. | |
| conversation_id | No | The conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation. | |
| idempotency_key | No | Optional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation. | |
| workspace_scope | No | Restrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| code | No | ||
| error | No | ||
| refused | No | ||
| success | Yes | ||
| prepared | No | ||
| reply_lines | No | ||
| conversation_id | No | The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation. | |
| near_candidates | No | ||
| newly_connected | No | Tools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later. | |
| already_prepared | No | ||
| conversation_id_note | No | Present only when the server opened a fresh lane, stating that no choice recorded earlier was read. | |
| conversation_id_source | No | Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened. | |
| near_candidates_truncated | No |