Markaestro

Official

by markaestro

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Create a post

create_post

Destructive

Create a social media post: omit scheduledAt to save a draft, or set a time to schedule publishing across one or more channels with uploaded media and channel settings.

Instructions

Create a post for this brand. Without scheduledAt the post is saved as a DRAFT and nothing is published; with scheduledAt it is scheduled and the worker publishes it at that time. Pass either a single channel or a targets array (one entry per channel). Upload media first with upload_media and pass the asset ids. Read channel rules with get_channel_rules before posting.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_post"
  }
}

Input Schema

Name	Required	Description
`caption`	No	Post text. Required on linkedin.
`channel`	No	Single channel. Mutually exclusive with targets.
`targets`	No	Several channels at once, each with its own destination and delivery mode.
`settings`	No	Platform settings for the single-channel form; __type must equal channel.
`productId`	No	Brand id from list_products. Required when this connection covers all brands in the workspace; a single-brand connection always uses its own brand and may omit it.
`scheduledAt`	No	Omit to save a draft.
`deliveryMode`	No	direct_publish: official platform API. manual_reminder: a timed reminder for a person to post natively (default on facebook, instagram, tiktok). platform_inbox: TikTok inbox handoff. Required when scheduling facebook, instagram, or tiktok.
`destinationId`	No	For the single-channel form, when the brand has several destinations on that channel.
`mediaAssetIds`	No	Asset ids from upload_media or list_media, in display order.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.4.0Nov 4, 2026

changedInput schema / properties / channel / enum

Previous value: -[
-  "facebook",
-  "instagram",
-  "tiktok",
-  "threads",
-  "pinterest",
-  "linkedin",
-  "x"
-]New value: +[
+  "facebook",
+  "instagram",
+  "tiktok",
+  "threads",
+  "pinterest",
+  "linkedin",
+  "x",
+  "youtube"
+]

changedInput schema / properties / targets / items / properties / channel / enum

Previous value: -[
-  "facebook",
-  "instagram",
-  "tiktok",
-  "threads",
-  "pinterest",
-  "linkedin",
-  "x"
-]New value: +[
+  "facebook",
+  "instagram",
+  "tiktok",
+  "threads",
+  "pinterest",
+  "linkedin",
+  "x",
+  "youtube"
+]

changedInput schema / properties / targets / items / properties / settings / description

Previous value: -"Platform settings with __type equal to the channel (instagram: postType, collaborators, altText; tiktok: postMode, privacyLevel, ...)."New value: +"Platform settings with __type equal to the channel (instagram: postType, collaborators, altText; tiktok: postMode, privacyLevel; youtube: title, privacyStatus, madeForKids; ...)."

First observedv0.3.3Sep 27, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true, openWorldHint=true, and idempotentHint=false, but the description adds genuinely useful context: nothing is published without scheduledAt, and with it a worker publishes at that time — which explains what the 'destructive' flag actually means here. It does not cover failure modes, validation errors, or what a partial multi-channel failure looks like, so it is not fully transparent.

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?

Four short sentences, front-loaded with the draft-vs-scheduled distinction that determines the tool's whole effect, then prerequisites, then parameter exclusivity. No filler or redundant restatement.

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 9-parameter, nested-object creation tool with zero required params and no output schema, the description covers the decision-critical behavior (draft vs. publish), the two mutually exclusive channel forms, media prerequisites, and the channel-rules prerequisite. Gaps are minor: nothing about which channels require caption (schema covers it), destinationId usage, or what is returned on success.

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 schema already documents every parameter's meaning, enum values, and nested settings. The description mainly restates this (channel vs. targets exclusivity, scheduledAt omission) and only adds the sourcing hint that media asset ids come from upload_media. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource ("Create a post for this brand") and immediately clarifies the two outcomes (draft vs. scheduled). It does not, however, differentiate itself from the sibling tools create_posts, bulk_posts, or publish_post, so an agent comparing them has no explicit routing hint.

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 concrete sequencing guidance: upload media with upload_media first, read get_channel_rules before posting, and pass either channel or targets. It also names the condition that changes behavior (omit scheduledAt = draft). It stops short of saying when to prefer this over create_posts, bulk_posts, or publish_post.

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