# schedule_post

> Schedule or unschedule an existing Blogizi post without rewriting its content.

HTML version: https://blogizi.com/docs/mcp-schedule-post
Markdown version: https://blogizi.com/docs/mcp-schedule-post.md

Schedule (or unschedule) an existing post without rewriting its content. Prefer this over rewriting the whole post when you only need to change the go-live time.

## Arguments

- `scheduledAt` — required; ISO or local `YYYY-MM-DDTHH:mm` in the project timezone, or `null` to clear
- `slug` or `postId` — one required
- `projectSlug` — required when the account has more than one project

## Schedule example

```json
{
  "slug": "how-we-built-our-auth-flow",
  "scheduledAt": "2026-10-26T09:00",
  "projectSlug": "my-app"
}
```

## Unschedule example

```json
{
  "slug": "how-we-built-our-auth-flow",
  "scheduledAt": null,
  "projectSlug": "my-app"
}
```

## Example result

```json
{
  "project": { "id": "665f…", "slug": "my-app", "timezone": "America/New_York" },
  "post": {
    "id": "666a…",
    "title": "How we built our auth flow",
    "slug": "how-we-built-our-auth-flow",
    "status": "draft",
    "scheduledAt": "2026-10-26T13:00:00.000Z"
  }
}
```

The post stays `status: "draft"` with a future `scheduledAt` until Blogizi publishes it. Agents should only call this when the user asked to schedule — not invent times or poll until publish. Use [publish_post](/docs/mcp-publish-post) only when the user asked to go live now.