PostPlanify

Create Post

create_post

Create and schedule a new social media post for one social account. socialAccountId comes from list_social_accounts. mediaIds come from: upload_attached_file (files attached in ChatGPT), open_upload_box (user uploads files from their device, best for local files and videos), create_upload_url + finish_upload (if you can run curl), upload_media_from_url (public links) or list_media. Pass mediaIds in carousel order.

PLATFORM NOTES:

Instagram: Requires at least 1 image or video. Set igTrialGraduationStrategy to post a single video as a Trial Reel
YouTube: Requires 1 video and youtubeParams.title
Pinterest: Requires pinterestParams.boardId (board IDs come from list_pinterest_boards)
TikTok: Requires at least 1 image or video
X/Twitter: Max 280 chars, max 4 media
Google Business: topicType STANDARD (default), EVENT, or OFFER. EVENT/OFFER require eventTitle + startDate + endDate.

scheduledAt must be a future ISO 8601 datetime.

Input Schema

Name	Required	Description
`caption`	No	The text content of the post
`isStory`	No	Post as a Story (Instagram/Facebook only)
`mediaIds`	No	Media IDs to attach (upload first), in carousel order
`scheduledAt`	Yes	Future ISO 8601 datetime (e.g. 2025-06-15T14:00:00Z)
`utmCampaign`	No	utm_campaign value added to links when shortenLinks is on
`workspaceId`	Yes	The workspace ID
`shortenLinks`	No	Shorten links in the caption with the workspace's connected Bitly account at publish time (ignored if Bitly is not connected)
`tiktokParams`	No	Required for TikTok posts
`xCommunityId`	No	X Community ID to post in
`xTaggedUsers`	No	X usernames to tag
`youtubeParams`	No	Required for YouTube posts
`pinterestParams`	No	Required for Pinterest posts
`socialAccountId`	Yes	The social account ID to post to
`googleBusinessParams`	No	Google Business post parameters
`igTrialGraduationStrategy`	No	Instagram only: post a single video (not a Story) as a Trial Reel, shown to non-followers first. MANUAL: the user decides in the Instagram app whether to share it with followers. SS_PERFORMANCE: Instagram shares it with followers automatically if it performs well

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

addedInput schema / properties / igTrialGraduationStrategy

Added value: +{
+  "description": "Instagram only: post a single video (not a Story) as a Trial Reel, shown to non-followers first. MANUAL: the user decides in the Instagram app whether to share it with followers. SS_PERFORMANCE: Instagram shares it with followers automatically if it performs well",
+  "enum": [
+    "MANUAL",
+    "SS_PERFORMANCE"
+  ],
+  "type": "string"
+}

Changed1 schema field changedOct 17, 2026

changedInput schema / properties / mediaIds / description

Previous value: -"Array of media IDs to attach (upload first)"New value: +"Media IDs to attach (upload first), in carousel order"

First observedOct 15, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations declare the write/open-world/non-destructive profile, and the description adds substantial context beyond that: scheduledAt must be a future ISO 8601 value, per-platform media requirements, carousel ordering, and Bitly-dependent link shortening. It stops short of describing post-creation outcomes or permission/failure behavior, so not a full 5.

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 main action followed by organized PLATFORM NOTES bullets; nearly every line earns its place. Minor redundancy exists where carousel order and boardId sourcing are restated relative to the schema, but overall it is efficient and scannable.

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 15-param tool with nested objects and no output schema, the description covers the hard parts: required per-platform params, media sourcing, and scheduling constraints. It doesn't describe what the tool returns (e.g., the created post ID) or failure behavior, but the description needn't cover return values and the structured fields handle the rest.

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 the baseline is 3, but the description genuinely adds value by giving cross-tool provenance for socialAccountId/mediaIds and spelling out conditional requirements per platform (YouTube title, Pinterest boardId, Google Business EVENT/OFFER dates). This goes beyond what the schema alone conveys.

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+resource+scope: 'Create and schedule a new social media post for one social account.' This clearly distinguishes it from siblings like edit_post, delete_post, and cancel_post without needing their schemas.

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 routes the agent to the right sibling for each dependency: socialAccountId from list_social_accounts, mediaIds from a named set of upload tools with conditions for each (ChatGPT attachments, local files, curl, public links), and boardId from list_pinterest_boards. Platform notes state exactly when special params become required, leaving little to inference.

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

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