Skip to main content
Glama

create_post_draft

Hold a post as a pending draft WITHOUT sending it. Nothing reaches any platform until you show the user the exact post, they say yes in chat, and you call approve_draft(draftId); a draft nobody approves expires after 24 hours and the post never goes out. Never tell the user to open the Socialync app to approve it: the whole flow stays in this chat. When the user has already confirmed the post, call publish_now instead (one step). Returns a draft_id, expiry, and dailyDraftsRemaining. Supports up to 10 images total via imageUrls (public https URLs) and/or base64Images (image bytes). Cannot attach video. Cannot draft to TikTok or YouTube (use schedule_post_draft for those). Instagram requires at least one image. Hard cap: 10 drafts per UTC day per profile -- platform-security mechanism to keep the user's accounts under Meta/X/LinkedIn spam-detection thresholds, not a Socialync restriction. ALWAYS run validate_post with these same arguments FIRST and resolve every error it reports before calling this.

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": {
      "caption": "<caption>"
    },
    "name": "create_post_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
captionYesPost caption/text. Will be shown to the user in the approval modal exactly as written.
imageUrlsNoUp to 10 publicly fetchable image URLs (https). Socialync copies them into its own storage when you call this tool, so the links only have to work right now (an expiring export link is fine). Per-platform image caps: X 4, Bluesky 4, LinkedIn 9, IG/FB/Threads 10. Combined with base64Images cannot exceed 10 total.
platformsNoPlatforms to draft for. One or more of: facebook, instagram, linkedin, twitter, threads, bluesky. TikTok/YouTube are not allowed here (use schedule_post_draft). Pass platforms OR audienceId, not both.
profileIdNoThe Socialync profile to post from. Call list_profiles to see the profiles you can post to. Required only when this connection is authorized for more than one profile; if exactly one is authorized it is used automatically.
audienceIdNoA saved audience id from list_audiences. Expands to the platforms that audience reaches on the target profile; any member it cannot reach (other brand, needs reconnect, secondary account without its primary) is reported back in skippedMembers instead of failing the call. Use INSTEAD of platforms, never together.
base64ImagesNoUp to 10 images encoded as base64 strings (data URIs like "data:image/png;base64,..." also accepted). Use this when the user uploaded image(s) to you directly. Socialync hosts them so the URLs are guaranteed reachable at publish time. Per-image cap: 8MB. Supported: jpeg, png, webp, gif. Combined with imageUrls cannot exceed 10 total.
firstCommentNoOptional "first comment": text Socialync posts as a comment under the post right after it publishes -- the classic home for hashtags and links, keeps the caption clean. One string for all platforms. Supported: instagram, threads, twitter, youtube, linkedin, bluesky. Facebook and TikTok do not support it (they record it as skipped; the post itself is unaffected). Per-platform comment length limits are enforced at draft time: instagram 2200, threads 500, twitter 280, youtube 10000, linkedin 1250, bluesky 300. A failed comment never fails the post.
exceptPlatformsNoOnly valid together with audienceId: platforms to leave out of the expanded audience for this one post (e.g. exclude tiktok when the post has no video).
platformSpecificSettingsNoPer-platform caption overrides if you want different wording for different platforms (e.g. shorter for Bluesky/Threads).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / platforms / description
      Previous value: -"Platforms to draft for. One or more of: facebook, instagram, linkedin, twitter, threads, bluesky. TikTok/YouTube are not allowed (video only). Pass platforms OR audienceId, not both."New value: +"Platforms to draft for. One or more of: facebook, instagram, linkedin, twitter, threads, bluesky. TikTok/YouTube are not allowed here (use schedule_post_draft). Pass platforms OR audienceId, not both."
  2. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful non-structured context: 24-hour expiry with no publish, the in-chat approval requirement, the 10-drafts-per-UTC-day cap and its rationale, and the no-video/Instagram-needs-image rules. However, it omits concurrency or idempotency behavior (e.g. what happens if the same draft is created twice) and any note on how draft expiry interacts with dailyDraftsRemaining, leaving a mid-range score for an otherwise rich disclosure.

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 behavior and approval rule in the first two sentences, and nearly every sentence carries operational information (expiry, caps, platform exclusions, validation precondition). It is dense but long, with approval-flow, image-limit, and platform-routing concerns interleaved rather than grouped, which costs it a point.

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?

For a 9-parameter, nested-object mutation tool with no output schema, the description still names the return fields (draft_id, expiry, dailyDraftsRemaining) and covers the constraints an agent must respect before calling. Nothing critical for a correct first invocation is missing.

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 description coverage is 100%, so the baseline is 3 and the schema carries most parameter meaning. The description still adds cross-parameter constraints not stated in the schema — 10 images total across imageUrls and base64Images, Instagram requires at least one image, and a pointer to schedule_post_draft for video platforms — which justifies a notch above baseline.

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?

Opens with a specific verb and resource plus an explicit scope negation: 'Hold a post as a pending draft WITHOUT sending it.' It distinguishes itself from approve_draft, publish_now, and schedule_post_draft by name, so an agent can route between them without opening 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?

Gives explicit when-to-use (user has not confirmed yet), when-to-use-the-alternative (publish_now once confirmed; schedule_post_draft for TikTok/YouTube), and a mandatory precondition (run validate_post first with the same arguments). Nothing is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.