MCP
schedule_post
Schedule or unschedule an existing Blogizi post without rewriting its content.
Schedule (or unschedule) an existing post without rewriting its content. Blogizi publishes at the scheduled time — agents should only call this when the user asked to schedule. Prefer this over rewriting the whole post when you only need to change the go-live time.
Arguments
scheduledAt— required; ISO or localYYYY-MM-DDTHH:mmin the project timezone, ornullto clearslugorpostId— one requiredprojectSlug— required when the account has more than one project
Schedule example
{
"slug": "how-we-built-our-auth-flow",
"scheduledAt": "2026-10-26T09:00",
"projectSlug": "my-app"
}Unschedule example
{
"slug": "how-we-built-our-auth-flow",
"scheduledAt": null,
"projectSlug": "my-app"
}Example result
{
"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. Do not invent times or poll until publish — use publish_post only when the user asked to go live now.