oriiion

Schedule Post

schedule_post

Schedule (or reschedule) a ready post for a date and time; it publishes itself then. Choose the networks with platforms — ['all'] for every connected network, or a subset like ['tiktok'] or ['linkedin','instagram']; omit to keep the post's current choice (else the account's publishing settings). instagramPlacement 'story' = Instagram story only; instagramTrialReel only when the user explicitly asks for a trial reel. Everything is checked now: the result lists the networks it will go to and any that can't publish, with the reason. For a NEW post on a date, use generate_posts with scheduledDate.

Input Schema

TableJSON Schema

Name	Required	Description
`postId`	Yes	The post ID to schedule
`platforms`	No	Which networks this post goes to. Omit to use the account's own publishing settings. ['all'] = every network the account has connected. Or any subset the user names, e.g. ['tiktok'], ['linkedin'], ['linkedin','instagram']. Only connected networks publish; the result lists any that can't, and why (not connected, switched off, needs a video).
`scheduledFor`	Yes	ISO 8601 datetime with UTC or offset for when to publish (e.g. 2026-10-26T09:00:00+01:00)
`facebookPlacement`	No	Facebook only: 'feed', 'story' (Page story only, no feed post, no caption) or 'feed_and_story'. Omit to keep the account default.
`instagramPlacement`	No	Instagram only: 'feed' = feed post, no story copy; 'story' = Instagram STORY ONLY — no feed post, no caption, first image or video only; 'feed_and_story' = feed post plus the same media as a story. Omit to keep the account default.
`instagramTrialReel`	No	Publish to Instagram as a TRIAL REEL (shown to non-followers first, kept off the profile grid; Instagram may share it with everyone if it performs well). Set true ONLY when the user explicitly asks for a trial reel for this post — never on your own. Needs a single video and Instagram among the networks. false withdraws it.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Discloses key behavior beyond annotations: rescheduling supported, automatic publishing at the scheduled time, immediate validation of networks, and result reporting for networks that cannot publish with reasons. The trial-reel caution adds important intent-level guidance.

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 action and followed by operational details. It is dense but mostly earns its space; a few platform details restate schema content.

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?

Covers the mutation nature, platform targeting, placement options, validation behavior, result expectations, and the alternative for new posts. No output schema exists, but the description explains what the result will list.

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 100%, so baseline is 3, but the description adds decision semantics beyond the schema — especially that omitting platforms keeps the post's current choice, falling back to account publishing settings, and that trial reels must only be set when explicitly requested. Some platform placement details duplicate 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?

States a specific verb and resource — schedule or reschedule a ready post for a date/time — and distinguishes itself from generate_posts for new scheduled posts. The publishing behavior ('it publishes itself then') is clear.

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?

Explicitly says when to use this tool versus generate_posts for a new post on a date. It also explains platform omission behavior, instagramPlacement story semantics, and the strict condition for instagramTrialReel.

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

All oriiion 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?