Schedule variants for future publishing
post_scheduleEnqueue channel variants with schedule_at for future publishing; variants without schedule_at are published immediately. Side effects: writes entries to the local YAML schedule store; makes external HTTP requests for any immediately-published variants; requires credentials in the named profile. Idempotent on (content.id, channel). Use post_schedule when any variant needs a future publish time; use post_publish for all-immediate delivery; use post_drain to process the scheduled queue later.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"content": "<content>",
"variants": "<variants>",
"profile_name": "<profile_name>"
},
"name": "post_schedule"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| content | Yes | Content piece to publish: stable id (idempotency key), title, body_md, tags, and optional cover_image / canonical_url / cta_block / author fields. The id + channel pair is the deduplication key — the same id will not be re-posted. | |
| variants | Yes | One or more channel-specific publish targets. Each entry specifies the channel slug, the adapted title and body, and optionally schedule_at (ISO-8601 with timezone) for future delivery. Variants without schedule_at are published immediately; variants with schedule_at are queued for post_drain. Use channel_hints to check per-channel constraints. | |
| profile_name | Yes | Name of the distribution profile (credentials store). Use profile_list to discover available names. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| results | Yes | Per-variant results, one entry per input variant in the same order. |