Skip to main content
Glama

Create or schedule a post

schedule_post

Creates a new post for one or more networks; to change a post that already exists, use update_post instead. Default status is "review": the post appears in the app with its date and waits for the user's approval before it is published. Status "scheduled" publishes automatically at scheduledAt, without approval (requires the publish scope); with scheduledAt "now" it goes out within a minute. Use "scheduled" only when the user explicitly asked to publish without approval; otherwise keep "review". X credits are checked before a scheduled post is accepted, and TikTok posts always need review. repeat (day, week or month) makes it a recurring post: each time it goes out, the next occurrence is created with the same content at the same time; update_post with repeat null stops the series. Always pass an idempotencyKey (for instance the source item's id or a date-based slug) so a retried call does not create a duplicate. Returns the post, or the validation errors when a network rule is broken. Network rules (the server enforces them; use overrides for a shorter text on one network):

  • x: 280 chars (links count 23); Every link counts as 23 characters. Up to 4 images or 1 video.

  • bluesky: 300 chars; Up to 4 images or 1 video (50 MB max). Without media, the first link becomes a preview card.

  • facebook: 63206 chars; Published on the linked Facebook Page. Without media, the first link becomes a preview card.

  • instagram: 2200 chars; Media required: one image, a carousel (up to 10 images) or one video (Reel). Links in the caption are not clickable.

  • tiktok: 2200 chars; Media required: one video or a set of images. Links are not clickable; hashtags are recognised. Cannot be scheduled from the API: use status review, the user picks the TikTok settings in Broadcast.

  • linkedin: 3000 chars; Published on the linked personal profile. Up to 20 images or 1 video. Without media, the first link becomes an article card.

  • mastodon: 500 chars; Up to 4 images or 1 video.

  • youtube: 5000 chars; One video required, no images. The text becomes the description; the title is its first line (100 chars max). Published public, not made for kids, unless changed in Broadcast. Vertical videos of 3 min or less become Shorts.

  • threads: 500 chars; Emojis count as their UTF-8 bytes. Up to 20 images (JPEG or PNG) or 1 video (MP4 or MOV, 5 min max), at most 5 links. Without media, the first link becomes a preview card. Only the first hashtag becomes a topic. firstComment (optional) is posted as a reply under the post on x, bluesky, linkedin, threads, mastodon, facebook and instagram, e.g. to keep a link out of a LinkedIn post; on X it costs credits like one more post. Dates are ISO 8601 with an offset; Europe/Paris is the user's time zone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesMain text of the post. Per-network overrides go in `overrides`; it may be empty ("") when every target has an override.
linkNoLink appended after the text (becomes a preview card on Bluesky, Mastodon, Threads, Facebook and LinkedIn without media).
mediaNoImages (up to 10 for most networks) or one video. Not both.
repeatNoPublishes the post again every day, week or month at the same time (Europe/Paris), counted from scheduledAt: once an occurrence goes out, the next one is created with the same content. null stops the series. TikTok settings chosen in the app apply to every occurrence.
statusNodraft: saved without a date. review (default when scheduledAt is set): waits for an approval in the app. scheduled: published automatically at scheduledAt, without approval (needs the publish scope); with scheduledAt "now" it goes out within a minute.
accountsNoTarget account ids (see GET /accounts / list_accounts).
hashtagsNoHashtags appended on their own line, with or without the leading #.
overridesNoText replacing `body` for one network, keyed by account id or platform name (e.g. a shorter text for x).
platformsNoAlternative to `accounts`: every connected account of these networks.
scheduledAtNoISO 8601 date-time with offset (e.g. 2026-10-14T09:00:00+02:00), or "now". Required for status review and scheduled.
firstCommentNoOptional reply Broadcast posts under the post right after it goes out, from the same account (e.g. the link, kept out of the post on LinkedIn, or the rest of a thread). Only on x, bluesky, linkedin, threads, mastodon, facebook and instagram; ignored elsewhere. Limits: 280 on x (links count 23), 300 on bluesky, 500 on threads and mastodon, 1250 elsewhere. On X it costs credits like one more post. If it fails, the post stays published and the target's comment.error says why.
idempotencyKeyNoClient-chosen key: a retried call with the same key returns the post already created instead of a duplicate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / body / description
      Previous value: -"Main text of the post. Per-network overrides go in `overrides`."New value: +"Main text of the post. Per-network overrides go in `overrides`; it may be empty (\"\") when every target has an override."
    • removedInput schema / properties / body / minLength
      Removed value: -1
  2. Changed2 schema fields changed
    • changedInput schema / properties / firstComment / description
      Previous value: -"Optional reply Broadcast posts under the post right after it goes out, from the same account (e.g. the link, kept out of the post on LinkedIn, or the rest of a thread). Only on x, bluesky, linkedin, threads, facebook and instagram; ignored elsewhere. Limits: 280 on x (links count 23), 300 on bluesky, 1250 elsewhere. On X it costs credits like one more post. If it fails, the post stays published and the target's comment.error says why."New value: +"Optional reply Broadcast posts under the post right after it goes out, from the same account (e.g. the link, kept out of the post on LinkedIn, or the rest of a thread). Only on x, bluesky, linkedin, threads, mastodon, facebook and instagram; ignored elsewhere. Limits: 280 on x (links count 23), 300 on bluesky, 500 on threads and mastodon, 1250 elsewhere. On X it costs credits like one more post. If it fails, the post stays published and the target's comment.error says why."
    • changedInput schema / properties / link / description
      Previous value: -"Link appended after the text (becomes a preview card on Bluesky, Facebook and LinkedIn without media)."New value: +"Link appended after the text (becomes a preview card on Bluesky, Mastodon, Threads, Facebook and LinkedIn without media)."
  3. Changed1 schema field changed
    • changedInput schema / properties / platforms / items / enum
      Previous value: -[
      -  "bluesky",
      -  "x",
      -  "facebook",
      -  "instagram",
      -  "tiktok",
      -  "linkedin",
      -  "mastodon",
      -  "threads"
      -]New value: +[
      +  "bluesky",
      +  "x",
      +  "facebook",
      +  "instagram",
      +  "tiktok",
      +  "linkedin",
      +  "mastodon",
      +  "threads",
      +  "youtube"
      +]
  4. Changed2 schema fields changed
    • changedInput schema / properties / firstComment / description
      Previous value: -"Optional reply Broadcast posts under the post right after it goes out, from the same account (e.g. the link, kept out of the post on LinkedIn, or the rest of a thread). Only on x, bluesky and linkedin; ignored elsewhere. Limits: 280 on x (links count 23), 300 on bluesky, 1250 on linkedin. On X it costs credits like one more post. If it fails, the post stays published and the target's comment.error says why."New value: +"Optional reply Broadcast posts under the post right after it goes out, from the same account (e.g. the link, kept out of the post on LinkedIn, or the rest of a thread). Only on x, bluesky, linkedin, threads, facebook and instagram; ignored elsewhere. Limits: 280 on x (links count 23), 300 on bluesky, 1250 elsewhere. On X it costs credits like one more post. If it fails, the post stays published and the target's comment.error says why."
    • changedInput schema / properties / platforms / items / enum
      Previous value: -[
      -  "bluesky",
      -  "x",
      -  "facebook",
      -  "instagram",
      -  "tiktok",
      -  "linkedin",
      -  "mastodon"
      -]New value: +[
      +  "bluesky",
      +  "x",
      +  "facebook",
      +  "instagram",
      +  "tiktok",
      +  "linkedin",
      +  "mastodon",
      +  "threads"
      +]
  5. First observed

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only supply the safety profile (readOnly=false, destructive=false); the description supplies everything else an agent needs to avoid a costly mistake: X credits are checked before acceptance, TikTok always needs review, most networks reject both media types, and validation errors are returned when a network rule breaks. The idempotencyKey guidance is consistent with idempotentHint=false (the call is only safe to retry when the client supplies a key).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The routing rule and status semantics are correctly front-loaded, and the per-network rules block earns its length because it exists nowhere in the schema. However, the paragraphs on status, repeat and firstComment restate their enum/property descriptions almost verbatim, so a meaningful share of the text duplicates structured data.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter, multi-network mutation with a nested media object and no output schema, the description supplies the failure contract ("Returns the post, or the validation errors"), the time-zone convention, and every platform constraint. Nothing needed to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not carry: per-network character/media limits, how overrides interact with body, that repeat chains occurrences counted from scheduledAt, and that firstComment is ignored on unsupported networks. It stops short of 5 only because the overrides and accounts/platforms relationships are left largely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb + resource ("Creates a new post for one or more networks") and immediately disambiguates from the sibling that shares its namespace: "to change a post that already exists, use update_post instead." An agent can route between schedule_post and update_post without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit conditional routing: use "review" unless the user explicitly asked to publish without approval, use "scheduled" only then, and use update_post with repeat null to stop a series. It also names the prerequisite (publish scope) and the platform exception (TikTok cannot be scheduled via API).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources