MCP tool reference · #433 of 563 by publishers
schedule_post
Exposed by 9 servers from 9 publishers, read from the live servers by the Serverdex check; most of them sit in Communication; 44.4% of them take a timezone parameter; the most-starred is Hermoso (8 stars).
schedule_post(timezone?: string, platforms?: array, postId: string, scheduled_at: string, scheduledAt: string, …)Parameters
share = % of the 9 servers whose schema has it · required = % of those that mark it required| Parameter | Type | Share | Required | Usual description |
|---|---|---|---|---|
| timezone | string | 44.4% | 0% | IANA time zone, e.g. Asia/Bangkok; the scheduledAt UTC offset specifies the exact instant. |
| platforms | array | 33.3% | 33.3% | Optional subset of platforms/account IDs |
| postId | string | 33.3% | 100% | Owner-bound postId from search_posts/search_post_drafts/create_post_draft. |
| scheduled_at | string | 33.3% | 100% | ISO 8601 datetime with timezone (e.g. 2030-01-01T09:00:00Z), or "now" to publish immediately. |
| scheduledAt | string | 33.3% | 100% | Exact publication time as ISO 8601 with UTC offset, e.g. 2026-10-29T10:00:00+07:00. Resolve the user time zone before scheduling. |
| title | string | 33.3% | 0% | Optional title for dashboard queue. |
| captions | object | 22.2% | 0% | Optional caption override per platform, e.g. {"x": "...", "linkedin": "..."}. |
| media | array | 22.2% | 0% | Optional media IDs from upload_media to attach before scheduling |
| platform | string | 22.2% | 50% | Platform of that connected account (must match it). |
| accounts | object | 11.1% | 0% | WHICH accounts of a multi-account channel to post to, e.g. { "tiktok": ["@a", "@b"] } or { "tiktok": "all" } — one row per account at fire time, each with its o |
| altText | — | 11.1% | 0% | ACCESSIBILITY — the screen-reader description of the image: what is IN the picture, never a repeat of the caption. One string covers every slide of a carousel; |
| at | string | 11.1% | 0% | when to post: local wall clock, no offset (2026-10-30T10:00), read in `timezone` or the brand’s zone ON THAT DATE so a series survives a clock change; or UTC (… |
Source: the input schema each server returns for schedule_post, aggregated over the 9 index-tier servers; type and description are the values most servers use. Rebuilt every 6 hours.
Servers with schedule_post
9 of 9 · 9 publishers · 9 answering live · most-starred first, 3 per publisher| # | Server | Publisher | Category | ★ | Live | How it describes schedule_post |
|---|---|---|---|---|---|---|
| 1 | Hermosohermoso-ai · Other | hermoso-ai | Other | 8 | yes | Use this to schedule a social media post for later, on one channel or several. Costs no credits (X alone bills per call: hermoso_credits). FREE PLAN: 5 posts a month on up to 3 channels (a post counts once; UTC month); paid plans are unlimited. Over it the post is refused and nothing is queued: relay the refusal as written, never retry or split the post. A MULTI-SLIDE creative goes in imageUrls[] |
| 2 | Social0abhishek-b-r · Communication | abhishek-b-r | Communication | 1 | yes | Schedule an existing unpublished Social0 draft for future publishing at a specific date and time. Example: 'Schedule tomorrow's announcement at 9 AM.' |
| 3 | Ravenposttarget1m · Communication | target1m | Communication | 1 | yes | Schedule (or reschedule) an existing post for a future time, without editing its content. Give scheduledAt as an absolute ISO 8601 datetime (include the offset, e.g. 2026-07-05T09:00:00+03:00). Rescheduling replaces the previous time, which is not kept. At that time the post is published to its target accounts, where it is public — tell the user the accounts and the time. A time less than 15 minut |
| 4 | Sirenhexahedral-inc · Business & CRM | hexahedral-inc | Business & CRM | — | yes | Schedule a finished run to post at scheduled_at (ISO-8601). Shows in the customer's local timezone. platforms: x, instagram, tiktok, linkedin, youtube, or everything. Posts fire sequentially. Requires Allow posting. Prefer this over post_run when the user names a time. On create_campaign you can pass scheduled_at instead. |
| 5 | PostWireperufitlife · Communication | perufitlife | Communication | — | yes | Use this when the user wants a social media post scheduled for later (a date and time, or the next free slot) on Instagram, TikTok, YouTube, LinkedIn, Facebook, X or another connected network. Queues a post to be published at a future time (run_at, ISO 8601 with timezone, up to 365 days ahead), or in the brand's next free queue slot (run_at "next_slot": the earliest weekly slot all its platforms s |
| 6 | MisarPost MCP Servermisar-ai · Productivity | misar-ai | Productivity | — | yes | Schedule a post to ONE connected account at a given time, or publish it immediately with scheduled_at="now". This queues real content for a real audience — show the user the exact text, account and time and get explicit approval first. To post the same content to several accounts, call once per account with the same post_batch_id. The user's post signature is appended server-side, and the safety g |
| 7 | SocialHivejalal1985khan · Marketing & SEO | jalal1985khan | Marketing & SEO | — | yes | Schedule an existing draft (or move a scheduled post) to an ISO 8601 time. Approval policy still applies. |
| 8 | Postlyraprof-1t · Content & Publishing | prof-1t | Content & Publishing | — | yes | Use when the author explicitly asks to schedule a post to a connected channel or group. Supply an exact ISO date with UTC offset and an idempotency key. The server uses the shared publishing rules and stores an immutable delivery snapshot. |
| 9 | NewsJackchrisschouk · Content & Publishing | chrisschouk | Content & Publishing | — | yes | Schedule a draft post for publishing at a designated future time. Supply content directly or reference existing content_id. |
Stars from GitHub as stored in the Serverdex index (re-read every 7 days per server); live = answered the last daily check of its hosted endpoint.