search_notes

Notes · macOS

Effect: read (strongest supported action). Status: gated.

Gated means the tool requires an installed app, a connected account, permission, or runtime availability. Check those requirements on the listed platform before using it.

macOS

Purpose

Searches Apple Notes by title or content. Paginated: `limit` is capped at 100 per call, so page with `offset` instead of asking for a bigger limit. The response carries `total` (how many notes match the query in all) and `has_more`, so a capped page is never mistaken for the complete answer — page until `has_more` is false, which is exact even when `total_is_estimated` says the count is only a lower bound. To walk every match, pass order="id" — see the order parameter.

Required inputs

query

Permissions and confirmation

No explicit confirmation parameter is exposed in this snapshot. This does not grant permission to act: obtain user authorization before any real action.

Use only the apps, accounts and resources authorized by the user on this platform. Consult this tool's platform-specific description for its connection and permission requirements; this catalog does not assert additional OAuth scopes or OS entitlements.

Full input schema — macOS

{
  "properties": {
    "limit": {
      "default": "20",
      "description": "Matches per page (default 20, capped at 100). To get more, page with offset.",
      "type": "integer"
    },
    "offset": {
      "default": "0",
      "description": "How many matches to skip (default 0). An offset past the end returns an empty page with has_more=false, not an error.",
      "minimum": 0,
      "type": "integer"
    },
    "order": {
      "default": "modified",
      "description": "order: \"modified\" (default) sorts newest-modified first — what you want to SHOW someone, but NOT safe for paging: modification date changes, so a note edited between two calls jumps to the front and another note is pushed past your cursor and never returned. \"id\" sorts by the note's immutable store id — stable, never renumbered, new notes append at the end — so use order=\"id\" to walk an entire library page by page: edits and insertions mid-crawl are safe with it. One case it cannot cover, because pages are addressed by offset: if a note is DELETED mid-crawl, every note after the hole shifts one slot back and the note that was on the page boundary is skipped, silently. If completeness matters, re-run the crawl and reconcile against total, or crawl while nothing is deleting notes.",
      "type": "string"
    },
    "query": {
      "type": "string"
    }
  },
  "required": [
    "query"
  ],
  "type": "object"
}

Documentation example

Do not execute this example. These concrete inputs refer to a fictional demonstration dataset. Resolve real handles and obtain user authorization before any real call.

{
  "query": "launch checklist"
}