Skip to main content
Glama

Create post

create_post

Create a draft, schedule a post, or publish now with publishNow=true using server time. Read account_context before batches to check plan, quota and maxScheduledDate. Publish Now consumes monthly publication quota but no deferred queue slot, so a full scheduled queue does not block it when monthly quota remains. FASTEST for media posts: pass mediaUrls (public https URLs — Publora downloads them server-side) together with scheduledTime or publishNow=true in one call; platforms like Instagram, TikTok, YouTube require media before scheduling. For a ChatGPT file, omit scheduledTime to create a draft (without publishNow=true), then use attach_media. Manual alternative for local files: omit scheduledTime to create a draft, upload media with get_upload_url + HTTP PUT + complete_media (once per file), verify ready with get_post, then call update_post with status 'scheduled' and scheduledTime, or publishNow=true.

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>",
      "platforms": "<platforms>"
    },
    "name": "create_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYesPost text content. On X and Threads, long content auto-splits into a chain; a standalone --- line between paragraphs sets a break, and media attach only to the first part. Threads parts are limited to 500 characters; the connection needs threads_manage_replies, and THREADS_PERMISSION_REQUIRED means reconnect in Publora Channels. Thread part and numbering settings are not API/MCP inputs. After partial publication, inspect get_post and never recreate or resubmit the whole chain. For an unknown outcome, check the live account before further action.
mediaUrlsNoOptional array (max 10) of public https URLs of images/videos to attach. Downloaded and validated server-side (jpeg, png, gif, webp, tiff, avif, mp4, mov, webm; images ≤25MB, videos ≤150MB). Must be DIRECT file URLs — share-page links (Google Drive, Dropbox pages) will fail.
platformsYesArray of platform identifiers in the exact format returned by list_connections. Each value must be the 'platformId' field copied verbatim from a connection object, e.g. ['twitter-1985855679454986200', 'linkedin-abc123']. IMPORTANT: Do NOT invent or guess IDs — always call list_connections first and use the exact platformId values. Exception: 'publora-playground' is a connection-test target that requires no real connection — the post is acknowledged and discarded, nothing is published; when used it must be the ONLY entry.
publishNowNoSet true to publish immediately using server time and trigger publication processing. Reserves monthly publication quota but does not occupy the deferred scheduled queue. Omit scheduledTime; a future time is rejected. False or omitted retains the existing draft/scheduling behavior. Publication remains asynchronous; inspect get_post for progress.
firstCommentNoLegacy single first comment under your own post. Supported: linkedin (profiles and Pages), twitter, threads, bluesky, mastodon; other targets are skipped. Best effort: read firstCommentResult via get_post. Cannot be combined with firstComments or added after publishing.
firstCommentsNoUp to 3 ordered first comments under your own post, each { text, platforms?, delaySeconds? }. delaySeconds is an integer 0–86400; omitted means 0. The next comment runs only after the previous one posts, on a scheduler tick; a failed comment stops later ones. Platform types (not connection keys) and text limits follow firstComment. Best effort, no blind retries. Read per-target firstCommentResults via get_post. Cannot be combined with firstComment or added after publishing.
scheduledTimeNoOptional ISO 8601 date-time with UTC Z or offset. Choose a future time within the schedule horizon returned by account_context; inspect returned warnings and effective scheduledTime. Omit to create a draft unless publishNow=true. With publishNow=true, omit this field; a future scheduledTime is rejected. Media-requiring platforms need mediaUrls in the same call or uploaded ready media before scheduling.
idempotencyKeyNoOptional retry key. Reusing it with the identical request replays the original response without creating another post.
platformSettingsNoPer-platform options keyed by platform. Example: { instagram: { coverUrl: 'https://.../cover.jpg' }, youtube: { title: 'My video', tags: ['topic'] }, tiktok: { viewerSetting: 'SELF_ONLY' }, twitter: { replyTo: 'https://x.com/user/status/123' } }. Also supports telegram.disableNotification/disableWebPagePreview/protectContent, threads.replyControl, linkedin.repostParentUrn/repostVisibility. For TikTok photos, tiktok.autoAddMusic lets TikTok choose music; no track selection or preview. Unknown platforms or fields are rejected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / platformSettings / properties / tiktok / properties / allowComments / description
      Added value: +"Default false for new posts. Enable comments only after the creator explicitly opts in; omission on update preserves the saved choice."
    • addedInput schema / properties / platformSettings / properties / tiktok / properties / allowDuet / description
      Added value: +"Default false for new posts. Enable Duet only after the creator explicitly opts in; omission on update preserves the saved choice."
    • addedInput schema / properties / platformSettings / properties / tiktok / properties / allowStitch / description
      Added value: +"Default false for new posts. Enable Stitch only after the creator explicitly opts in; omission on update preserves the saved choice."
  2. Changed4 schema fields changed
    • addedInput schema / properties / platformSettings / properties / instagram / properties / aiGenerated
      Added value: +{
      +  "description": "Self-disclose AI-generated content: adds Instagram's \"AI info\" label (is_ai_generated). Required by Meta for realistic AI-generated or AI-altered video, audio or images. Cannot be added or removed after publishing. Default false.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / platformSettings / properties / tiktok / properties / aiGenerated
      Added value: +{
      +  "description": "Self-disclose AI-generated content: adds TikTok's \"Creator labeled as AI-generated\" label (is_aigc). Required for realistic AI-generated video or images; missing disclosure risks removal or loss of For You eligibility. Default false.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / platformSettings / properties / twitter / properties / aiGenerated
      Added value: +{
      +  "description": "Self-disclose that the post contains AI-generated media (X made_with_ai, shown as \"Made with AI\"). Sent only when the post attaches media; a text-only post is published without it. Voluntary on X in general; mandatory for AI videos of armed conflicts by creators in revenue sharing. Default false.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / platformSettings / properties / youtube / properties / aiGenerated
      Added value: +{
      +  "description": "Self-disclose altered or synthetic content (status.containsSyntheticMedia). Required for realistic AI-generated or AI-altered video or audio; not needed for scripts, titles, thumbnails, beauty filters or clearly unrealistic content. Default false.",
      +  "type": "boolean"
      +}
  3. Changed2 schema fields changed
    • changedInput schema / properties / platformSettings / description
      Previous value: -"Per-platform options keyed by platform. Example: { instagram: { coverUrl: 'https://.../cover.jpg' }, youtube: { title: 'My video', tags: ['topic'] }, tiktok: { viewerSetting: 'SELF_ONLY' }, twitter: { replyTo: 'https://x.com/user/status/123' } }. Also supports telegram.disableNotification/disableWebPagePreview/protectContent, threads.replyControl, linkedin.repostParentUrn/repostVisibility. Unknown platforms or fields are rejected."New value: +"Per-platform options keyed by platform. Example: { instagram: { coverUrl: 'https://.../cover.jpg' }, youtube: { title: 'My video', tags: ['topic'] }, tiktok: { viewerSetting: 'SELF_ONLY' }, twitter: { replyTo: 'https://x.com/user/status/123' } }. Also supports telegram.disableNotification/disableWebPagePreview/protectContent, threads.replyControl, linkedin.repostParentUrn/repostVisibility. For TikTok photos, tiktok.autoAddMusic lets TikTok choose music; no track selection or preview. Unknown platforms or fields are rejected."
    • addedInput schema / properties / platformSettings / properties / tiktok / properties / autoAddMusic
      Added value: +{
      +  "description": "Photo Direct Post only. Opt in with true to let TikTok automatically choose music; Publora cannot select or preview a specific track. False disables music and is allowed when switching to video. Omission preserves existing behavior. Videos never send this parameter.",
      +  "type": "boolean"
      +}
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare non-readonly, open-world, non-idempotent, non-destructive; the description adds quota semantics that annotations cannot express — Publish Now consumes monthly publication quota but not a deferred queue slot, so a full queue does not block it. It further discloses asynchronous publication, best-effort comments with no blind retries, partial-chain handling, and idempotencyKey replay behavior.

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

Conciseness4/5

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

It is front-loaded with mode selection and the fastest media path, and each workflow branch earns its sentence. Some quota and publishNow/scheduledTime rules are restated twice (once in the description, again in the publishNow and scheduledTime field descriptions), which is mild redundancy for a description this long.

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

Completeness4/5

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

For a 9-parameter mutation tool with nested platformSettings and no output schema, the description covers workflow, quota, and platform constraints thoroughly. The one real gap is what a successful call returns (e.g., a post identifier) — it points to get_post for progress but never says the create response yields the handle needed to call it.

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 already 100%, so the baseline is 3; the description earns above that by clarifying cross-parameter interaction the schema states only per-field: publishNow and scheduledTime are mutually exclusive, and a future scheduledTime is rejected when publishNow=true. It does not add much on firstComment/firstComments or platformSettings beyond what those field descriptions already say, which keeps it at 4 rather than 5.

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 and resource plus the three mutually exclusive modes ('Create a draft, schedule a post, or publish now with publishNow=true'), so an agent immediately knows the tool's scope. It also routes to concrete sibling tools (attach_media, get_upload_url, complete_media, update_post, get_post) rather than leaving alternatives implicit.

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 when-to-use rules and a preferred path: read account_context before batches, use mediaUrls in one call as FASTEST, and fall back to the draft + get_upload_url/HTTP PUT/complete_media + update_post sequence only for local files. It also states the failure mode selecting the wrong path (media-requiring platforms like Instagram/TikTok/YouTube need media before scheduling).

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.