Octopost

Schedule a post

schedule_post

Schedule a post for future publishing. The Octopost scheduler will publish it at the specified time automatically.

The post is saved as a draft until the scheduled time, then published to all specified platforms.

Same platform limits and same options as create_post, which documents them in full. Options are saved with the post and applied when it publishes.

Set needs_approval=true to hold it for a person to approve first (same flow as queue_post).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "content": "<content>",
      "platforms": "<platforms>",
      "scheduled_for": "<scheduled_for>"
    },
    "name": "schedule_post"
  }
}

Input Schema

Name	Required	Description
`poll`	No	Poll, 2-4 options (Twitter and Mastodon only). See create_post.
`tiktok`	No	For TikTok. See create_post.
`content`	Yes	The post text
`accounts`	No	Optional. Which account per network when a platform has several, e.g. {"twitter": "@handle"}. See create_post.
`segments`	No	Optional thread replies (up to 24). See create_post.
`variants`	No	Optional. A different version per network, e.g. {"linkedin": {"content": "..."}}; what it leaves out comes from the main post. See create_post.
`platforms`	Yes	Which platforms to post to
`video_url`	No	Optional video URL.
`media_urls`	No	Optional images or one video: URLs or {url, alt}. See create_post.
`first_comment`	No	Optional. Posted as the first reply right after the post. See create_post.
`scheduled_for`	Yes	When to publish, ISO 8601. With a timezone offset or Z, e.g. 2026-11-04T09:00:00-05:00 or 2026-11-04T14:00:00Z (a time without one is rejected). Must be in the future.
`needs_approval`	No	If true, the post is held until a person approves it (Octopost emails them a one-tap link). Approved before scheduled_for: it publishes then; approved later: it publishes right away. Default: false.
`allow_duplicate`	No	Optional. true to send text already sent to that network within 7 days (refused otherwise). See create_post.
`content_warning`	No	Mastodon content warning.
`idempotency_key`	No	Optional. Unique string for this post: a retry with the same key returns the original post. See create_post.
`primary_platform`	No	Which platform goes first when cross-linking.
`cross_link_enabled`	No	Post to primary_platform first, then share its link on the others. See create_post.
`cross_link_template`	No	Cross-link text, with {platform} and {link}. See create_post.
`mastodon_visibility`	No	Mastodon visibility. Default: public.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations only declare it is not read-only, is open-world and non-destructive. The description adds real behavioral context: the post is persisted as a draft until the scheduled time and then auto-published to all specified platforms, and options are stored and applied at publish time. It does not discuss what happens on failure at publish time or how the scheduled item can later be cancelled, which limits it to a 4.

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 core action and lifecycle, then routing. The pair 'Same platform limits and same options as create_post... Options are saved with the post and applied when it publishes' is mildly redundant but still earns its place by clarifying that validated options carry through to publish time.

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 19-parameter mutation tool with nested objects and no output schema, the description covers lifecycle, delegation to create_post, and the approval branch, which is enough to call it correctly. It omits what the call returns (e.g., a scheduled post id) and how the scheduled item is later modified or cancelled, which are the remaining gaps.

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 every one of the 19 parameters is already documented, making 3 the baseline. The description adds a useful pointer that platform limits and option semantics are documented in full in create_post, but it contributes no additional meaning for any individual parameter.

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 plus a distinguishing qualifier: 'Schedule a post for future publishing.' That separates it from create_post (immediate) and queue_post (approval/queue flow) without the agent needing to open either 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 routing: use this for future publishing, and 'Set needs_approval=true ... (same flow as queue_post)' for the approval variant. It also delegates option semantics to create_post. It stops short of an explicit exclusion such as 'to publish immediately use create_post' and never mentions reschedule_post/cancel_scheduled as follow-ups.

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

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