schedule_notes

DescriptionCopy Anchor Link

The description the MCP server sends to the model, word for word. Its rules apply to every call.

Schedule notes to the user's next available posting slots based on their recurring schedule template. Each note is routed by its own tags: first open or matching reserved lane. Untagged notes only use open or untagged-only slots. You can also set or update each note's autoRestackAfterHours at the same time (1–168 hours; null clears it). To also cross-post the notes to Buffer channels when they publish, pass bufferChannelIds (call list_buffer_channels first to get valid IDs) — the same channels are applied to every note in the batch, except a slot with its own Buffer channels replaces those for the note that lands there. Queue routing: each weekly time can reserve tags, accept only untagged notes, or stay open for any note, and may also set default Buffer channels. A time with tags is a reserved lane — it stays empty until a note shares ANY of those tags (OR). A time marked untaggedNotesOnly (and with no tags) accepts only notes with no tags; tagged notes never take those times, including Add to Queue leftovers. Untagged notes never take reserved lanes. When filling the next template times (schedule_notes), a tagged note takes the first open (any-note) time or matching reserved lane, whichever comes first. An untagged note takes the first open or untagged-only time. If a time has Buffer channels, those replace the note's channels when the note lands there (apply-on-schedule only). Substack still always posts. Call get_schedule to see each slot's tags, untaggedNotesOnly, and bufferChannels. You MAY create notes without asking. CRITICAL: Scheduling in WriteStack does NOT push notes to Substack. After scheduling, the user must open WriteStack and click the yellow Sync/Warning button so the Chrome extension syncs them — you cannot do this for them. BEFORE calling this tool, you MUST ask the user to confirm they understand they need to sync manually afterward, then pass userConfirmedManualSync: true. Never set that flag unless they explicitly confirmed in this conversation. IMPORTANT: Call get_schedule_capacity first. NEVER, under any circumstances, schedule more than the reported remaining (unless unlimited=true). If the user asks to schedule more than remaining, schedule only the first remaining notes, leave the rest as ready/drafts, and tell the user how many were scheduled and why the rest were not. Scheduling sets the notes' status to scheduled and assigns posting times; this integration cannot unschedule them, so the user would have to undo it in WriteStack.

ArgumentsCopy Anchor Link

Example callCopy Anchor Link

The smallest valid request: required arguments only, with placeholder values.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "schedule_notes",
    "arguments": {
      "noteIds": [
        "…"
      ],
      "userConfirmedManualSync": true
    }
  }
}

ResultCopy Anchor Link

The result has structuredContent that matches this schema. The same data is also in content as JSON text.

AnnotationsCopy Anchor Link

The full input and output JSON Schemas for every tool are in /mcp-tools.json.