Request: add notebookName as a param to evernote_update_note

[rob-ditoro]

Hey there, could you please expose notebookName (or even just notebook GUID) to evernote_update_note? Would allow moving of notes across notebooks.

[jack-arturo]

@autojack can you look into this?

[autojack-bot]

Looked into this. Good news: notebookName was already added to evernote_update_note on main — merged in #45 ("inject live notebook names into tool descriptions") and preserved through the later tool-consolidation refactor in #62.

• Schema: src/tool-schemas.ts:57 — notebookName: z.string().trim().min(1, ...).optional() on UpdateNoteSchema
• Tool description: src/index.ts:775 — "Move note to this notebook (full-update mode)"
• Handler: src/index.ts:2026 resolves the notebook by name (auto-creating it if it doesn't exist, same behavior as evernote_create_note) and reassigns note.notebookGuid before saving.

So on main, calling:

{ "guid": "<note-guid>", "notebookName": "Target Notebook" }

against evernote_update_note moves the note to that notebook (full-update mode; not compatible with the replacements[] patch mode in the same call).

However, this hasn't shipped to npm yet. The published package (@verygoodplugins/mcp-evernote@1.2.3) is from January 2026, before PR #45 merged (June 2026) — so anyone installing via npx @verygoodplugins/mcp-evernote today does not have notebookName support. There's an open, unmerged Release Please PR (#39, "release mcp-evernote 2.0.0") sitting since May 2026 that bundles this fix plus everything else merged since — it just needs review/merge to publish. Flagging that as the actual blocker here for @jack-arturo.

@rob-ditoro if you're building from main you can use this today; if you're on the published npm package, it'll land once #39 is merged and republished.