AdaptlyPost

Create Post

create_post

Create and schedule a post to one or more platforms. Pass connection IDs from list_accounts to target specific accounts. Omit scheduledAt to post immediately, or set saveAsDraft to save without publishing. For platform-specific options (YouTube titles, TikTok privacy, Pinterest boards, Instagram post type), use the corresponding platform configs.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`text`	No	Default post text shared across platforms
`pageIds`	No	Facebook page IDs
`timezone`	No	IANA timezone (e.g. "America/New_York")	UTC
`mediaUrls`	No	Media URLs to attach. Use publicUrl values from upload_media or get_upload_urls
`platforms`	Yes	Target platforms (e.g. ["LINKEDIN", "TWITTER"])
`contentType`	Yes	Content type: TEXT, IMAGE, VIDEO, or CAROUSEL
`saveAsDraft`	No	Save as draft instead of publishing
`scheduledAt`	No	ISO 8601 datetime to schedule (e.g. "2026-03-15T10:00:00Z"). Omit to post immediately
`thumbnailUrl`	No	Custom thumbnail image URL for video posts
`platformTexts`	No	Per-platform caption overrides
`tiktokConfigs`	No	TikTok per-connection config. Each entry needs connectionId + privacyLevel at minimum
`youtubeConfigs`	No	YouTube per-connection config with video title, tags, privacy, etc.
`facebookConfigs`	No	Facebook per-page config with post type and video title
`instagramConfigs`	No	Instagram per-connection config to set post type (FEED, REEL, STORY)
`pinterestConfigs`	No	Pinterest per-connection config. boardId is required for Pinterest posts
`tiktokConnectionIds`	No	TikTok account connection IDs to post from
`blueskyConnectionIds`	No	Bluesky account connection IDs to post from
`threadsConnectionIds`	No	Threads account connection IDs to post from
`thumbnailTimestampMs`	No	Generate thumbnail from video at this timestamp (milliseconds)
`twitterConnectionIds`	No	X (Twitter) account connection IDs to post from
`youtubeConnectionIds`	No	YouTube channel connection IDs to post from
`linkedinConnectionIds`	No	LinkedIn account connection IDs to post from
`instagramConnectionIds`	No	Instagram account connection IDs to post from
`pinterestConnectionIds`	No	Pinterest account connection IDs to post from

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	No	The created post record including its id, status, and scheduled time as returned by the AdaptlyPost API.

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already signal this is a mutating operation (readOnlyHint=false, destructiveHint=false), and the description adds useful behavior: scheduling vs immediate publishing, draft behavior, and delegation to platform configs. It does not describe every side effect, but the annotations and output schema reduce the burden on the description.

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?

Three sentences with no filler. The main action is front-loaded, and each sentence adds a distinct decision or category: connection targeting, scheduling/draft behavior, and platform-specific configs.

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 high-complexity, 24-parameter tool, the description supplies the essential workflow: how to target accounts, how to choose immediate vs scheduled vs draft, and where to find platform-specific settings. The schema covers detailed parameters and an output schema exists, so the description is reasonably complete for an agent selecting and invoking this 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?

Schema description coverage is 100%, so the baseline is 3 and the schema already explains scheduledAt, saveAsDraft, contentType, and connection IDs. The description adds only high-level grouping ('use the corresponding platform configs') and references list_accounts, which is also in the schema, so it does not materially expand parameter meaning.

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 opens with a specific action and resource: 'Create and schedule a post to one or more platforms.' It immediately distinguishes this tool from siblings by covering scheduling, immediate posting, draft saving, and platform-specific options, while also referencing list_accounts for connection IDs.

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?

The description gives clear operational guidance: pass connection IDs from list_accounts, omit scheduledAt for immediate posting, set saveAsDraft to avoid publishing, and use platform configs for platform-specific settings. It does not explicitly mention alternatives like bulk_schedule_posts or update_post, so exclusions are absent rather than explicitly stated.

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

All AdaptlyPost 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.2/5.0

Disambiguation4/5

Most tools are clearly separated by resource and action, but get_post and list_post_results both expose per-platform publishing status/errors, which could cause misselection. create_post and bulk_schedule_posts are closely related, though the descriptions make the single-vs-bulk distinction clear.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern: create_post, list_posts, upload_media, retry_failed_platforms, etc. Even multi-word actions like bulk_schedule_posts preserve the same style, making the naming predictable and easy to navigate.

Tool Count5/5

With 12 tools, the set is well-scoped for a social media scheduling server. It covers post lifecycle management, bulk operations, media handling, account discovery, and retries without feeling bloated or sparse.

Completeness5/5

The tool surface covers the full publishing workflow: account listing, media upload, post creation, scheduling, listing, retrieval, updating, deletion, draft publishing, retry, and per-platform result inspection. Limitations like not updating published posts reflect expected platform constraints rather than missing server functionality.

Resources

Need Help?