schedule_notes_with_custom_dates

DescriptionCopy Anchor Link

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

Schedule notes at user-provided custom dates/times (one date per note). ONLY use this tool if: (1) the user explicitly requests specific dates/times for their notes, OR (2) the user has no recurring schedule template set up (schedule_notes returned an error about a missing template). In all other cases, prefer schedule_notes with the recurring template instead — that tool honors reserved tag lanes. Custom dates skip lane preference because you pick the time; if the chosen time matches a slot that has Buffer channels, those still replace the note's channels. All dates must be in the future. Pass dates as ISO 8601 strings (e.g. 2026-05-01T14:30:00Z). You can also set or update each note's autoRestackAfterHours at the same time (1–168 hours; null clears it), and cross-post each note to Buffer channels by passing per-note bufferChannelIds (call list_buffer_channels first to get valid IDs). 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_with_custom_dates",
    "arguments": {
      "notes": [
        {
          "noteId": "…",
          "scheduledAt": "…"
        }
      ],
      "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.