PostNitro

Update Scheduled Post

postnitro_update_scheduled_post

DestructiveIdempotent

Update an existing scheduled post or draft. The body and validation mirror postnitro_create_scheduled_post exactly.

The update REPLACES the post's captions and selected accounts with what you send — send the full intended state, not just changed fields. Tip: call postnitro_get_scheduled_post first to read the current values.

Input Schema

TableJSON Schema

Name	Required	Description
`status`	Yes	'DRAFT' or 'SCHEDULED'
`designId`	No	ID of a design in your workspace to attach. This is the design ID (the `designId` field from a carousel's output / postnitro_get_output), NOT the generation job's embedPostId — passing an embedPostId here fails with 'Design not found.' A post must have either a designId or non-empty postContent. May only be null/omitted for DRAFT.
`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.
`scheduledAt`	Yes	ISO-8601 datetime string. Must be in the future (for both drafts and scheduled posts).
`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.
`scheduledPostId`	Yes	The scheduled-post ID to update (get from postnitro_list_scheduled_posts)
`selectedAccounts`	No	Social-account IDs to publish to (from postnitro_list_social_accounts). The platforms among these determine which *PostSettings are required.
`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
`warnings`	No	Non-fatal issues worth surfacing to the user (e.g. AI image generation did not complete)
`scheduledPostId`	Yes	ID of the scheduled post — pass to get/update/delete

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.1/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds the critical disclosure that the update REPLACES captions and selected accounts wholesale rather than patching, and that callers must send full intended state. That is meaningful behavior beyond the annotations, though it doesn't cover auth/permission requirements.

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?

Four short sentences, front-loaded with the action and immediately followed by the highest-risk behavior (replacement). Every sentence is functional; the 'Tip:' phrasing is slightly informal but still earns its place.

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 13-parameter, nested-schema mutation tool with an output schema present, the description covers the one thing the schema cannot convey — full-replacement semantics and the read-before-write recommendation. It leaves platform-specific rules to the schema, which is acceptable given 100% coverage.

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

Parameters3/5

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

Schema description coverage is 100%, so the 13 parameters (including nested platform settings) are already documented in the schema. The description only cross-references create_scheduled_post for parameter semantics, adding little syntax or format detail of its own, so the baseline 3 applies.

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 verb and resource ('Update an existing scheduled post or draft') and implicitly contrasts with postnitro_create_scheduled_post for new posts and postnitro_get_scheduled_post for reads. An agent can distinguish this from all nearby siblings without opening a schema.

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?

Gives clear context ('update an existing scheduled post or draft') and a concrete workflow tip: call postnitro_get_scheduled_post first to read current values. It also points to create_scheduled_post as the body/validation reference. It lacks an explicit 'when not to use' (e.g., use create for new posts), so it stops 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?