PostNitro

Generate Carousel and Schedule It

postnitro_generate_and_schedule

Convenience tool: generates a post with AI (postType 'CAROUSEL' by default, 'IMAGE' for a single-image post, or 'VIDEO' for a video), waits for it to finish, then creates a scheduled post that attaches the resulting design. May take 30-180 seconds (longer for a rendered video).

templateId, brandId, presetId, and responseType are optional if saved via postnitro_set_defaults.

The design that gets attached is the completed carousel's design ID (result.designId from the generation output) — NOT the generation job ID. You normally don't set designId; it's resolved automatically. Pass designId only to attach a pre-existing design instead of the freshly generated one.

If scheduling fails after the carousel is already generated (e.g. an invalid platform-settings combination), this tool returns the generated designId so you can fix the inputs and retry with postnitro_create_scheduled_post — WITHOUT regenerating (which would burn credits again).

Provide the scheduling fields (status, scheduledAt, selectedAccounts, captions, and any required per-platform settings) just as you would for postnitro_create_scheduled_post.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`status`	Yes	'DRAFT' or 'SCHEDULED'
`brandId`	No	Brand ID (optional if saved via postnitro_set_defaults)
`designId`	No	Attach a pre-existing design instead of the freshly generated one. Leave unset to use the generated carousel's design.
`postType`	No	'CAROUSEL' (default) generates a multi-slide carousel; 'IMAGE' generates a single-image post; 'VIDEO' generates a video whose slides are its scenes. The rest of the request is identical, except VIDEO also accepts videoSettings and only supports responseType 'MP4' or 'DESIGN'.	CAROUSEL
`presetId`	No	AI preset ID (optional if saved via postnitro_set_defaults)
`templateId`	No	Template ID (optional if saved via postnitro_set_defaults)
`postContent`	No	Caption text keyed by platform. Required unless a designId is set; at least one key must be non-empty. Hashtags are extracted automatically.
`requestorId`	No	Optional custom tracking ID
`scheduledAt`	Yes	ISO-8601 datetime string. Must be in the future.
`aiGeneration`	Yes
`postSettings`	No	Video render settings, used when any resolved postType is 'reel'. Optional: when omitted, the API fills each field from the videoSettings the attached design was generated with, falling back to 30 seconds with no audio. Same shape as a VIDEO post's videoSettings.
`responseType`	No	Output format. 'DESIGN' (default) creates the design with no rendered file — fastest, and enough for scheduling/editing. Use 'PDF' or 'PNG' when you need a rendered file back, or 'MP4' for a rendered video (postType 'VIDEO' only). Optional if saved via postnitro_set_defaults.
`videoSettings`	No	Video render settings — postType 'VIDEO' only. Required when responseType is 'MP4'. Scheduling a reel reuses these automatically, so you usually don't also need postSettings.
`generateImages`	No	Optional AI image generation — include this object to enable it, omit it for no images. When included, `context` is required and you (the agent) must author it from the post. Best-effort: the post still COMPLETES if images fail or aren't permitted (free plan / exhausted AI-image quota); check the GENERATE_IMAGES step via postnitro_check_status. Requires a paid plan, consumes the org's AI-image quota (separate from post credits), and adds latency.
`selectedAccounts`	No	Social-account IDs to publish to (from postnitro_list_social_accounts)
`tiktokPostSettings`	No	Required when a TikTok account is selected AND a designId is set. When SCHEDULED: if isBrandedContent is true, at least one of isYourBrand/isThirdPartyBrand must be true, and isBrandedContent cannot be true with privacyLevel SELF_ONLY.
`threadsPostSettings`	No	Required when a Threads account is selected AND a designId is set
`facebookPostSettings`	No	Required when a Facebook Page is selected AND a designId is set. A designId is required when status is SCHEDULED (Facebook Pages can't take text-only posts from PostNitro).
`linkedinPostSettings`	No	Required when a LinkedIn account is selected. A designId is required when status is SCHEDULED (text-only LinkedIn posts can only be drafts).
`instagramPostSettings`	No	Required when an Instagram account is selected AND a designId is set
`pinterestPostSettings`	No	Required when a Pinterest board is selected AND a designId is set. A designId is required when status is SCHEDULED (Pinterest can't take text-only Pins). Each board is its own connected account, so there is no board field here — pick boards via selectedAccounts.

Output Schema

TableJSON Schema

Name	Required	Description
`post`	Yes	A scheduled post or draft
`message`	Yes	Confirmation message
`success`	Yes
`designId`	Yes	The design attached to the scheduled post
`warnings`	No	Non-fatal issues worth surfacing to the user (e.g. AI image generation did not complete)
`embedPostId`	Yes	The generation/import job ID
`scheduledPostId`	Yes	ID of the created scheduled post

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 7, 2026

addedInput schema / properties / pinterestPostSettings

Added value: +{
+  "additionalProperties": false,
+  "description": "Required when a Pinterest board is selected AND a designId is set. A designId is required when status is SCHEDULED (Pinterest can't take text-only Pins). Each board is its own connected account, so there is no board field here — pick boards via selectedAccounts.",
+  "properties": {
+    "link": {
+      "description": "Destination URL the Pin links to. Optional, but must be an absolute http(s) URL, e.g. https://example.com.",
+      "type": "string"
+    },
+    "postType": {
+      "description": "'carousel' = a carousel Pin (2-5 slides; a 1-slide design publishes as an image Pin, more than 5 slides fails); 'image' = a single image Pin; 'reel' = a video Pin (uses postSettings like other platforms' reels). Any design size works except ultra-wide (wider than 21:9); 2:3 is recommended.",
+      "enum": [
+        "carousel",
+        "image",
+        "reel"
+      ],
+      "type": "string"
+    },
+    "title": {
+      "description": "Pin title, up to 100 characters. Optional.",
+      "maxLength": 100,
+      "type": "string"
+    }
+  },
+  "required": [
+    "postType"
+  ],
+  "type": "object"
+}

addedInput schema / properties / postContent / properties / pinterest

Added value: +{
+  "description": "Pinterest Pin description. Only the first 800 characters are published.",
+  "type": "string"
+}

addedOutput schema / properties / post / properties / pinterestPostSettings

Added value: +{
+  "$ref": "#/properties/post/properties/instagramPostSettings"
+}

Changed3 schema fields changedSep 29, 2026

addedInput schema / properties / facebookPostSettings

Added value: +{
+  "additionalProperties": false,
+  "description": "Required when a Facebook Page is selected AND a designId is set. A designId is required when status is SCHEDULED (Facebook Pages can't take text-only posts from PostNitro).",
+  "properties": {
+    "callToAction": {
+      "anyOf": [
+        {
+          "enum": [
+            "BOOK_TRAVEL",
+            "BUY_NOW",
+            "CALL_NOW",
+            "DOWNLOAD",
+            "GET_DIRECTIONS",
+            "GET_QUOTE",
+            "INSTALL_APP",
+            "INSTALL_MOBILE_APP",
+            "LEARN_MORE",
+            "LIKE_PAGE",
+            "LISTEN_MUSIC",
+            "MESSAGE_PAGE",
+            "NO_BUTTON",
+            "OPEN_LINK",
+            "PLAY_GAME",
+            "SHOP_NOW",
+            "SIGN_UP",
+            "SUBSCRIBE",
+            "USE_APP",
+            "USE_MOBILE_APP",
+            "WATCH_MORE",
+            "WATCH_VIDEO"
+          ],
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "'link_carousel' only. Button shown on the carousel, e.g. 'LEARN_MORE' or 'SHOP_NOW'. Omit or null for no button. Some types are meant for ads and Facebook may reject them on organic posts."
+    },
+    "linkUrl": {
+      "description": "'link_carousel' only. The absolute http(s) URL every card links to, e.g. https://example.com. Required when status is SCHEDULED. Facebook only accepts custom card images for links on a domain the Page's business has verified in Meta Business Settings.",
+      "type": "string"
+    },
+    "postType": {
+      "description": "'carousel' = every slide in one multi-photo post; 'link_carousel' = swipeable link cards (2-10 slides; Facebook shows up to 5 and picks which); 'image' = a single-slide design; 'reel' = a video, published as a Reel (any aspect ratio from 16:9 to 9:16).",
+      "enum": [
+        "carousel",
+        "link_carousel",
+        "image",
+        "reel"
+      ],
+      "type": "string"
+    },
+    "showEndCard": {
+      "description": "'link_carousel' only. Show Facebook's end card linking to the Page. Defaults to true.",
+      "type": "boolean"
+    },
+    "useSlideDescriptions": {
+      "description": "'link_carousel' only. Use each slide's description as its card description. Defaults to false.",
+      "type": "boolean"
+    },
+    "useSlideTitles": {
+      "description": "'link_carousel' only. Use each slide's title as its card headline. Defaults to false (Facebook uses the link's own title).",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "postType"
+  ],
+  "type": "object"
+}

addedInput schema / properties / postContent / properties / facebook / description
```
Added value: +"Facebook Page caption (the post message)"
```

addedOutput schema / properties / post / properties / facebookPostSettings

Added value: +{
+  "$ref": "#/properties/post/properties/instagramPostSettings"
+}

First observedSep 7, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare the generic write/non-idempotent/open-world profile; the description adds substantive operational context the annotations cannot: 30-180s latency, credit burn on regeneration, and the partial-success behavior of returning a designId so the agent can retry scheduling without re-generating.

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?

Front-loaded with the core purpose and no filler sentences — each paragraph (defaults, designId resolution, failure/retry) carries distinct information. Slightly long for the channel, but nothing is redundant with the schema.

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 21-parameter tool with nested platform settings, an output schema, and annotations, the description supplies exactly the cross-cutting context the structured fields omit: the generate-then-schedule flow, latency, credit economics, and the partial-failure contract. Return-value detail is correctly left to the output schema.

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 already 95%, setting a baseline of 3, and the description genuinely adds meaning on top: the designId-vs-generation-job-ID distinction, the resolution of designId automatically, and the defaults-based optionality of templateId/brandId/presetId/responseType.

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?

States a specific composite action (AI-generate then schedule) with concrete defaults and post types, and the 'Convenience tool' framing immediately distinguishes it from the atomic siblings postnitro_generate_and_wait and postnitro_create_scheduled_post.

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?

Explains optional fields when defaults are saved and explicitly routes the agent to postnitro_create_scheduled_post for retry-without-regeneration after a scheduling failure. It implies but never states the inverse condition (when to prefer the two atomic tools over this convenience wrapper), so it stops just short of a 5.

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

All PostNitro tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?