Jade Note

Pass actor when you already have a named agent identity. Jade Note uses it as the note's author label. Prefer that identity over the MCP client/host. Omit actor if you do not have one; do not invent a name or send a generic label. DEPRECATED for new edits. Use edit_note with patches instead. This remains callable to apply an in-flight preview_note_patch token. Repeated calls return already_applied without writing again.

apply_note_patch

Pass actor when you already have a named agent identity. Jade Note uses it as the note's author label. Prefer that identity over the MCP client/host. Omit actor if you do not have one; do not invent a name or send a generic label. Use this only after a preview_note_update result and a later explicit user confirmation. Apply the exact signed preview_token once; repeated calls return already_applied without writing again. A category change may enqueue saved category-assigned triggers, which can send configured push or email notifications.

apply_note_replace

Pass actor when you already have a named agent identity. Jade Note uses it as the note's author label. Prefer that identity over the MCP client/host. Omit actor if you do not have one; do not invent a name or send a generic label. Use this only after a preview_note_update result, a deprecated preview_note_* result, or an in-flight edit preview, and a later explicit user confirmation. Apply the exact signed proposal once; repeated calls return already_applied without writing again. A replace proposal that changes category may enqueue saved category-assigned triggers, which can send configured push or email notifications. For new title, body, field, pin, or importance edits, use edit_note.

apply_note_update

Pass actor when you already have a named agent identity. Jade Note uses it as the note's author label. Prefer that identity over the MCP client/host. Omit actor if you do not have one; do not invent a name or send a generic label. Use only after a later user message explicitly confirms a batch of signed previews. Applies each note independently and reports partial failures without rolling back successful notes. A replace proposal that changes category may enqueue saved category-assigned triggers, which can send configured push or email notifications.

apply_note_updates

Create a Pro or active Trial manual note-history checkpoint before a broad MCP edit.

checkpoint_note

Pass actor when you already have a named agent identity. Jade Note uses it as the note's author label. Prefer that identity over the MCP client/host. Omit actor if you do not have one; do not invent a name or send a generic label. Compatibility-only tool for an already-published metadata snapshot. Create a formatted-category record only when no existing record has the exact normalized match fields; never update an existing record. Creating a record may enqueue saved note-created triggers, which can send configured push or email notifications.

create_category_record_if_absent

Pass actor when you already have a named agent identity. Jade Note uses it as the note's author label. Prefer that identity over the MCP client/host. Omit actor if you do not have one; do not invent a name or send a generic label. Use this when the user asks to create a Jade Note note from Markdown body and optional category/properties/pin state. If list_categories reports has_instructions for the destination, read those instructions from get_category_wiki before creating the note, and follow them. To change category instructions, use preview_category_instructions. For a formatted category, pass field IDs and values in properties; if the required field IDs or allowed values are not already known, call get_category_schema first. Pass session_url only when the current ChatGPT or Claude conversation URL is explicitly available; omit it rather than guessing. To reference another existing note in the body, write [[Exact Note Title]], then call create_note_link for that pair so it renders as a linked reference instead of plain text. To assign existing tags, call list_note_tags first and pass resolved tag_ids; never invent tags. Prefer 0-3 clear existing matches and select none if uncertain. Call create_note_tag only when the user explicitly asks to create a new tag, then pass that ID in tag_ids. Returns a compact receipt unless return_body=true. Creating a categorized note may enqueue saved note-created triggers, which can send configured push or email notifications.

create_note

Use this when the user asks to create a new reusable flag definition. It does not assign the flag to a note; call add_note_flag after if the user also wants it on a note. Call list_note_flags first and reuse an existing name when one already fits. Creating a definition sends no notifications. notification_on_add defaults to false; enabling it makes later assignments email the user. Configure webhook connections with configure_flag_webhook or in the Jade Note Flags screen. Webhook configuration requires Pro or Trial. Explain this before enabling notifications.

create_note_flag

Create an explicit link between two existing Jade Note notes. Both note IDs must come from a prior Jade Note read or search result. Do not invent note IDs. Use find_link_candidates only when the intended target is not already known.

create_note_link

Create multiple explicit outgoing links from one existing Jade Note note. Each target may have its own relation. Both the source ID and every target ID must come from a prior Jade Note read or search result. Do not invent note IDs. Use find_link_candidates only when the intended target is not already known. Existing source/target/relation pairs are skipped as already_exists. Other items may succeed or fail independently.

create_note_links

Use this when the user explicitly asks to create a new reusable tag definition. Ordinary tag selection should reuse existing tags from list_note_tags; do not create a tag only because no existing tag fits. This creates a definition only and does not assign it to a note. If the user also wants it on a note, call add_note_tag with the returned ID, or pass that ID as tag_ids to create_note.

create_note_tag

Soft-delete a Jade Note note by ID and remove it from the retrieval index best-effort.

delete_note

Soft-delete one comment from a note by comment ID and remove it from the retrieval index. Use this only when the user explicitly asks to delete that specific comment; never call it as a side effect of another request.

delete_note_comment

Delete an explicit Jade Note note link by link ID.

delete_note_link

Pass actor when you already have a named agent identity. Jade Note uses it as the note's author label. Prefer that identity over the MCP client/host. Omit actor if you do not have one; do not invent a name or send a generic label. Atomically apply one title, append, exact-patch, full-body replacement, current-category field, pin, or importance edit without a separate confirmation. These changes may be combined, except body cannot be combined with append_body or patches. Applied edits return changed fields, a compact diff summary, and guarded Undo arguments. If list_categories reports has_instructions for the note's category, read those instructions from get_category_wiki before editing, and follow them. To reference another existing note in the body, write [[Exact Note Title]], then call create_note_link for that pair. For category moves or authority metadata, use preview_note_update.

edit_note

Pass actor when you already have a named agent identity. Jade Note uses it as the note's author label. Prefer that identity over the MCP client/host. Omit actor if you do not have one; do not invent a name or send a generic label. Apply independent title, append, patch, full-body, current-category field, pin, or importance edits to multiple notes. Each note is atomic and has a durable retry receipt; the batch may partially succeed. Applied items include a diff summary and guarded Undo arguments. If list_categories reports has_instructions for a note's category, read those instructions from get_category_wiki before editing that note, and follow them. To reference another existing note in a body, write [[Exact Note Title]], then call create_note_link for that pair.

edit_notes

Read the current category wiki, freshness status, changed-note deltas, and user-authored instructions before category-level discussion. Follow instructions for structure and note conventions. This tool never generates or saves a wiki, applies note maintenance, or queues work.

ensure_fresh_category_context

Discover candidate notes when the intended link target is not already known. Defaults to hybrid semantic/keyword search and returns a deterministic combined ranking score plus semantic_score and lexical_score components. The score is not a probability. Hybrid mode merges and reranks both semantic and keyword candidates. Existing outgoing relations are preserved; title mentions suggest references; all other matches suggest related. If a real target note ID is already known from search_notes, list_notes, get_note, or list_note_links, call create_note_link or create_note_links directly. Do not infer IDs from note titles or [[Title]] text.

find_link_candidates

Read one Catch Up receipt by receipt_id, including the compact change preview and whether Undo is still available. This tool never applies or undoes Catch Up.

get_category_maintenance_receipt

Get the typed fields, system columns, base view, and Markdown-body capability for a visible formatted category.

get_category_schema

Get the dedicated Jade Note category wiki by category name or category UUID. Also returns the category's user-authored instructions (its SKILL.md), even when the wiki is missing. Follow instructions for structure and note conventions in this category. To change instructions, use preview_category_instructions; do not use update_category_wiki. The wiki body cites source notes via source citation lines using note:<ID> Markdown links, and source_note_ids lists those referenced note IDs. Follow them with get_note to drill into a claim instead of re-searching.

get_category_wiki

Get a full Jade Note note by ID, including explicit outgoing note links and backlinks. The root note includes comment_count, including 0. Call list_note_comments when you need the comment bodies.

get_note

List active notes whose source starts with mcp:, optionally filtered by client slug.

list_mcp_created_notes

List active Jade Note categories visible to MCP, including category wiki IDs, access levels, and has_instructions. This list does not include the instructions body; call get_category_wiki, or ensure_fresh_category_context on Pro, to read it.

list_categories

List comments on a Jade Note note by ID, ordered oldest to newest.

list_note_comments

Use this when note results reference flag IDs or when the user wants to inspect reusable note flag definitions. Returns definitions and email/webhook notification status without connection secrets. delivery_paused=true means assignment does not send to that connection.

list_note_flags

List explicit outgoing note links and backlinks around a Jade Note note by ID.

list_note_links

Use this when the user asks which tags exist, or before selecting tag IDs for create_note, list_notes, search_notes, add_note_tag, or remove_note_tag. Returns compact MCP-visible definitions. Unused tags remain discoverable; tags used only on hidden notes do not. Prefer 0-3 clear existing matches, select none if uncertain, and never invent tag IDs or names. Call create_note_tag only when the user explicitly asks to create a new tag.

list_note_tags

List saved versions for a Pro or active Trial Jade Note note.

list_note_versions

List active Jade Note notes by default, optionally filtered by category name, an MCP-visible flag UUID, or MCP-visible tag UUIDs using OR. Notes in hidden MCP categories are omitted. By default, pinned notes come first, then notes are ordered by updated_at descending and id descending. Set sort to updated_at ascending or descending to ignore pin position. Set include_archived=true only when the user asks for archived notes. Each note includes comment_count, including 0. Call list_note_comments only when those comment bodies are needed. Set include_body=true to include Markdown bodies; this caps the result limit at 10. Use offset for best-effort pagination; notes changed between calls may move between pages.

list_notes

Diagnose which active MCP-visible notes are not yet reflected in semantic search: pending (never indexed) or stale (indexed but out of date). Use this instead of scanning search_notes/list_notes results when the user asks why a note isn't showing up in semantic search. pending_count/stale_count are exact totals; the pending/stale lists are bounded by limit/offset.

list_semantic_index_issues

DEPRECATED. Do not use this tool. Use edit_note instead. Pass actor when you already have a named agent identity. Jade Note uses it as the note's author label. Prefer that identity over the MCP client/host. Omit actor if you do not have one; do not invent a name or send a generic label. Safely patch a note body by replacing one unique exact Markdown snippet. Rejects missing or multiple matches and applies expected_updated_at atomically. Returns a compact receipt unless return_body=true.

patch_note

Preview a change to a category's user-authored instructions (its SKILL.md) without saving them. Keep the written instructions as short and specific as possible. Show the returned diff, then stop. Do not call apply_category_instructions until a later user message explicitly confirms this exact preview. If the user changes the request, create a new preview. Do not use update_category_wiki to change instructions. Empty or null instructions clears them.

preview_category_instructions

Use this when the user asks to delete a reusable flag definition. Returns a signed preview with the flag and how many MCP-visible notes currently have it assigned. Show the preview and stop. Do not call apply_delete_note_flag until a later user message explicitly confirms this exact preview. Apply deletes the definition for the whole account, including notes MCP cannot show. This does not persist a delete and does not unassign a single note; use remove_note_flag to remove one assignment.

preview_delete_note_flag

DEPRECATED. Do not use this tool. Use edit_note with append_body instead. This tool remains callable for compatibility: it validates an append and saves a private confirmation proposal without changing the note. The proposal can be confirmed for up to 24 hours; expired proposals are removed by scheduled cleanup.

preview_note_append

DEPRECATED. Do not use this tool. Use edit_note with fields instead. This tool remains callable for compatibility: it validates typed field changes and saves a private confirmation proposal without changing the note. The proposal can be confirmed for up to 24 hours; expired proposals are removed by scheduled cleanup.

preview_note_fields_update

DEPRECATED. Do not use this tool. Use edit_note with patches instead. This tool remains callable for compatibility: it validates one exact Markdown replacement and saves a private confirmation proposal without changing the note. The proposal can be confirmed for up to 24 hours; expired proposals are removed by scheduled cleanup.

preview_note_patch

Use this when the user wants to change a note's category, authority_status, or successor. Title, body, properties, pin, and importance may be included in the same preview. For title, body, fields, pin, or importance alone, use edit_note. Validate and normalize the proposed changes, then save a private confirmation proposal without changing the note. The proposal can be confirmed for up to 24 hours; expired proposals are removed by scheduled cleanup. Wait for explicit confirmation before apply_note_update. Omitted properties are preserved during category changes when they are compatible with the target schema; pass properties explicitly to replace or clear them.

preview_note_update

Query a formatted category with schema-aware filters, a single sort, projection, keyword search, or semantic search constrained to structured candidate record IDs.

query_category_records

Generate and replace a dedicated Jade Note category wiki from active notes in one category, then update note importance and explicit note links for the same source notes. Inbox refreshes may also move high-confidence notes to existing categories. After a successful Catch Up, summarize the returned summary and any preview reasons, and tell the user they can revert remaining Catch Up changes with undo_category_maintenance using receipt_id while Undo remains available. Later edits to individual fields are left unchanged. Do not mention credit refunds, the Undo expiry date, or that later edits will block Undo.

refresh_category_wiki