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
`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

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. Dates show when Glama detected each change.

First observedSep 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The description explicitly states that the update REPLACES captions and accounts, disclosing destructive behavior beyond the annotations. It also mentions the need to send the full state, which is useful behavioral detail. No contradiction with annotations.

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

Conciseness5/5

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

The description is two concise sentences, front-loading the core behavior and a key tip. No unnecessary words or redundancy.

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?

Given the schema's high coverage, the description does not need to repeat parameter details. It adds the essential context of replace semantics and a retrieval tip, making it sufficient for an agent to correctly invoke the tool.

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?

The schema descriptions already cover 100% of parameters, so the baseline is 3. The tool description adds a general note about replace semantics and a tip, but does not provide additional parameter-specific meaning beyond 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?

The description clearly states the tool updates an existing scheduled post or draft, with a specific verb and resource. It also distinguishes itself by mentioning it mirrors the create tool, making its purpose unambiguous.

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?

It provides guidance on when to use it (updating vs. creating) and includes a practical tip to call the getter first. It does not explicitly name alternative tools but clearly implies the update counterpart to the create tool.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation4/5

Most tools are clearly separated by verb and noun (generate_carousel vs generate_image vs generate_video, import_* vs generate_*). The generic convenience names like generate_and_wait and import_and_wait are slightly ambiguous, but their descriptions and the _wait/_schedule suffixes make them distinguishable.

Naming Consistency4/5

All tools share the postnitro_ prefix and snake_case verb-first convention. A few compound names (generate_and_schedule, import_and_wait) break the strict verb_noun pattern, but the convention is otherwise consistent and predictable.

Tool Count2/5

With 35 tools, the surface exceeds the rubric's 25+ 'too many' threshold. Many entries are convenience wrappers (_wait, _and_schedule) around the same core operations and could be consolidated to reduce overload.

Completeness4/5

The domain is well covered: generation, import, output retrieval, scheduling, brands, social accounts, audio, templates, presets, and defaults. Minor gaps remain (no delete_brand, no upload/connect for audio/social accounts), but those are largely external or non-critical.

Resources

Need Help?