Skip to main content
Glama

Create post

create_post

Create a post on any Flomixy channel (Instagram, Threads, Facebook, LinkedIn, TikTok, Telegram, Pinterest, YouTube, WordPress, Bluesky, Google Business Profile; a pin always needs media, accountId is the board, and optional pinTitle/pinLink/pinAltText set the pin title, destination link and alt text; THREADS accepts an optional topicTag, the topic tag (community) the post is published under, so it reaches the community feed beyond followers) via channel + accountId, or on several networks at once via targets (each with optional caption/media/scheduledAt/firstComment overrides), for YouTube see below; optionally proposing a publish time with scheduledAt (ISO 8601 with time zone). An optional firstComment (+ firstCommentDelayMinutes) is posted as the first comment after publish, per target or post-wide (Links in Instagram and Facebook comments are NOT clickable: on FACEBOOK put the link (e.g. the blog URL) in the caption itself, on its own last line, and do not use firstComment for a link; on INSTAGRAM use "link in bio". Threads comments keep clickable links.). By default the post needs human approval and never goes live directly; optional approval can route it to a specific reviewer (see list_approvers) or, only for a key the owner granted POSTS_AUTO_APPROVE, skip review. Optional recyclingEnabled (+ recyclingIntervalDays/MaxRepeats/ExpiresAt) sets up Evergreen recycling for once the post is PUBLISHED; requires the POSTS_RECYCLE scope. YOUTUBE posts a video (accountId is the channel; a video is required, text-only and image posts are rejected; the caption is the video description). ytTitle and ytMadeForKids are REQUIRED on a YOUTUBE target; optional ytPrivacyStatus, ytSyntheticMedia, ytCategoryId, ytTags, ytNotifySubscribers, ytThumbnailUrl. postType "reel" publishes a Short (max length in get_channel_capabilities maxShortSeconds). YouTube has no first comment: firstComment on a YOUTUBE target fails with UNSUPPORTED_ON_CHANNEL. When the youtube flag is off the call fails with an error, it never publishes silently. Uploads are capped by YouTube's daily API quota; an over-quota publish waits for the reset instead of failing. BLUESKY posts text-first (accountId is the Bluesky account; no media is required): the caption is limited to 300 GRAPHEMES (what the user sees, maxCaptionGraphemes in get_channel_capabilities), longer text fails with a validation error before anything is saved. Up to 4 images (bskyAltTexts = alt text per image in order) OR one video, never both; links, @mentions and #hashtags in the text become clickable on their own and bskyLinkPreview adds a link card. Optional bskyReplyGate, bskyDisableQuotes, bskyContentLabels. firstComment IS supported on BLUESKY (posted as a reply to the post, links are clickable). Analytics have no impressions/reach. When the bluesky flag is off the call fails with an error, it never publishes silently. GBP posts to a Google Business Profile location (accountId is the location; the post text is the caption, limited to 1500 Unicode CODE POINTS = maxCaptionChars in get_channel_capabilities; at most ONE image, no video, text-only is fine). gbpPostKind is UPDATE (default), EVENT or OFFER: EVENT and OFFER REQUIRE gbpEventTitle, gbpEventStart and gbpEventEnd (a missing one fails with a typed GBP_EVENT_FIELDS_REQUIRED error before anything is saved); an OFFER may add gbpOfferCoupon, gbpOfferUrl, gbpOfferTerms. gbpCtaType (BOOK, ORDER, SHOP, LEARN_MORE, SIGN_UP need gbpCtaUrl; CALL takes no URL). GBP has no first comment (firstComment fails with UNSUPPORTED_ON_CHANNEL). Analytics are per location (get_account_analytics: available=false with a reason when the location is unreachable) and get_best_times is not available for GBP. When the gbp feature is off the call fails with an error, it never publishes silently. WORDPRESS publishes a blog article to a connected site (accountId is the site; postType is always ARTICLE; no media is required). title and one of contentHtml / contentMarkdown are REQUIRED on a WORDPRESS target; optional excerpt, slug, categories, tags, wpStatus (publish/draft/pending), featuredImage, featuredImageAlt. Look up real category and tag ids with list_wordpress_categories; never invent them. The article body is NOT the caption. WordPress has no first comment (UNSUPPORTED_ON_CHANNEL) and no account analytics; article metrics come from the Google Analytics of the site only when it is linked (get_post_metrics). When the wordpress feature is off the call fails with an error, it never publishes silently. A post created without scheduledAt and without publishNow stays a draft: it is NOT scheduled and will never publish by itself. If the user did not say when to publish, ask them for a time before creating the post. For "publish now" use publishNow:true together with approval:{mode:"none"}, but only if the API key allows it (POSTS_AUTO_APPROVE); otherwise propose a scheduledAt and tell the user a human must approve. If the user wants a post with an image/video but gave no URL or media id, ask first which they prefer: (a) a public link, (a2) a file the AI itself produced: upload_media with contentBase64 (one file per call, up to 10 MB, no manual step), (b) upload via a Flomixy upload link (create_upload_link; with shell access curl the returned uploadEndpoint, no base64), (c) pick from the media library (list_media), (d) a stock photo (search_stock_photos, images only), (e) generate with AI: generate_image (images only, monthly quota), (f) no media, only if the network allows it (see get_channel_capabilities). If media is already provided, do not ask.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNo
tagsNo
titleNo
ytTagsNo
captionNoPost caption. The limit depends on the channel (e.g. Instagram 2200, LinkedIn 3000 bytes). URLs are not clickable on Instagram/TikTok: write "link in bio" there (see get_channel_capabilities linkInBioOnly).
channelNoPublishing channel, canonically UPPERCASE (e.g. INSTAGRAM); lowercase is accepted too. Single-network form; omit when using `targets`.
excerptNo
pinLinkNo
targetsNoOne post for several networks (1-6). Use INSTEAD of channel + accountId.
ytTitleNo
approvalNoApproval routing. Omit for the default: approval required, no specific approver.
pinTitleNo
postTypeNoPost format, canonically lowercase (image, carousel, reel, story); uppercase is accepted too. Defaults to image. A story takes ONE media item; a story video must be 3-60 seconds long (9:16 recommended), otherwise a scheduled story is rejected.
topicTagNo
wpStatusNo
accountIdNoThe Flomixy account id for `channel` (required with `channel`).
gbpCtaUrlNo
mediaUrlsNoMedia URLs for the post (http/https only).
categoriesNo
gbpCtaTypeNo
mediaTypesNoMedia types, e.g. ["image"].
pinAltTextNo
publishNowNoPublish right away (within about a minute). Use ONLY when the user explicitly asked to publish immediately. Requires approval.mode "none" and an API key with the owner-granted POSTS_AUTO_APPROVE scope (403 otherwise); cannot be combined with scheduledAt. A brand that forces approval still holds the post.
alsoShareToNoWORDPRESS article only: after the article is created, ALSO create one linked social post per listed network (e.g. ["INSTAGRAM","LINKEDIN"]), written by AI from the article text and scheduled 10 minutes after the article. The same result as "Generate social posts" in Flomixy, in this one call. Requires wpStatus "publish" (a draft has no public URL) and exactly one connected account per listed network in the article's brand; networks that cannot be matched, or an exhausted AI caption quota, are reported as skipped while the article itself is still created. Never include WORDPRESS.
contentHtmlNo
gbpEventEndNo
gbpOfferUrlNo
gbpPostKindNo
scheduledAtNoProposed publish time, ISO 8601 WITH time zone, e.g. 2026-10-01T09:00:00Z or +02:00. Must be at least 10 minutes from now, otherwise SCHEDULED_TOO_SOON (not retryable; the error names the earliest allowed time).
bskyAltTextsNo
firstCommentNoFirst comment posted right after the post goes live. With `targets` it applies to every eligible target (INSTAGRAM not Story, THREADS, FACEBOOK, BLUESKY; never YOUTUBE or GBP) without its own firstComment. Links in Instagram and Facebook comments are NOT clickable: on FACEBOOK put the link (e.g. the blog URL) in the caption itself, on its own last line, and do not use firstComment for a link; on INSTAGRAM use "link in bio". Threads comments keep clickable links.
ytCategoryIdNo
bskyReplyGateNo
featuredImageNo
gbpEventStartNo
gbpEventTitleNo
gbpOfferTermsNo
ytMadeForKidsNo
gbpOfferCouponNo
idempotencyKeyNoUnique key for this logical post (1-255 chars). Reuse it when retrying: the same key + same input within 24h returns the original post instead of creating a duplicate.
ytThumbnailUrlNo
bskyLinkPreviewNo
contentMarkdownNo
featuredMediaIdNoWORDPRESS only (single-network form): featured image from the media library (id from list_media or upload_media) instead of a URL. Use this OR featuredImage, not both; with targets set it on the WORDPRESS target.
ytPrivacyStatusNo
featuredImageAltNo
recyclingEnabledNoEvergreen: once this post is PUBLISHED, re-draft it every recyclingIntervalDays (never auto-published; a human must approve each re-draft). Requires an API key with the POSTS_RECYCLE scope (403 otherwise).
ytSyntheticMediaNo
bskyContentLabelsNo
bskyDisableQuotesNo
recyclingExpiresAtNoStop recycling after this instant (ISO 8601 with time zone); must be in the future. Omit for never.
recyclingMaxRepeatsNoStop recycling after this many re-drafts. Omit for unlimited.
ytNotifySubscribersNo
recyclingIntervalDaysNoDays between recycles. Required when recyclingEnabled is true and the post has no interval stored yet.
firstCommentDelayMinutesNoMinutes after publish before firstComment is posted. Omit/0 = right after (~90s).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations at all, the description carries the full burden and does so unusually well: default human approval and never going live directly, the POSTS_AUTO_APPROVE scope requirement with 403 otherwise, feature-flag failures that error rather than publish silently, YouTube daily quota behavior (waits for reset instead of failing), pre-save validation errors (GBP_EVENT_FIELDS_REQUIRED, TAG_NOT_FOUND, SCHEDULED_TOO_SOON), and per-channel unsupported-operation errors (UNSUPPORTED_ON_CHANNEL). This is exactly the non-obvious destructive/permission/limit context an agent needs before calling a write tool.

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?

Every sentence carries real information — there is little filler — but the structure is poor: one enormous paragraph with deeply nested parentheses and mid-sentence channel switches. The critical constraints (approval default, need for a scheduled time, publishNow preconditions) sit after a wall of channel-specific trivia, so front-loading is weak. It is sized for the tool's complexity but not organized for retrieval.

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 an 11-channel, 55-parameter write tool with no annotations and no output schema, the description covers an impressive amount: per-channel media/format rules, approval routing, recycling scope, scheduling constraints, and the media-sourcing decision tree. What is missing is what the call returns (post id, approval status?) and any mention of idempotencyKey retry semantics, both of which an agent needs to handle the response and retry safely.

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 description coverage is only 35% across 55 parameters, so the description must compensate and largely does: it explains the pin field trio, THREADS topicTag semantics, firstComment link-clickability rules per network, ytTitle/ytMadeForKids being required on YouTube, gbpPostKind gating event fields, wpStatus, and contentHtml/contentMarkdown as the article body rather than the caption. Several parameters (idempotencyKey, alsoShareTo, sequence, mediaTypes, bskyAltTexts, excerpt) get no narrative treatment, though most are covered by inline schema descriptions.

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

Purpose4/5

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

The opening clause gives a specific verb and resource ("Create a post on any Flomixy channel") and enumerates the eleven supported channels, so the agent knows exactly what the tool does. It also spells out the two mutually exclusive shapes (single channel + accountId vs. `targets` for multi-network). It loses a point because a sibling `create_draft_post` exists and the description's line "a post created without scheduledAt and without publishNow stays a draft" blurs the boundary with that sibling without naming it.

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

Usage Guidelines4/5

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

Strong routing guidance: it tells the agent to ask the user for a publish time when none was given, to use publishNow only with approval.mode "none" and the POSTS_AUTO_APPROVE scope, and it names concrete alternatives for media sourcing (upload_media, create_upload_link, list_media, search_stock_photos, generate_image, get_channel_capabilities). It also states exclusions such as "If media is already provided, do not ask." The remaining gap is the unnamed create_draft_post/update_post boundary, which an agent must infer.

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