Skip to main content
Glama

Post one video to several platforms

clipember_create_post

Schedule (or post now, or save as a draft) ONE video to several platforms at once, each with its own caption. The video is either the user's own (mediaId from clipember_upload_media_from_url) or a rendered clip (clipId). One target per account: each account must be connected (clipember_list_platform_connections) unless mode is "draft", and when a platform has several accounts each target names its connectionId (each account once). YouTube Shorts and Instagram Reels WILL publish publicly to the user's account at the set time — confirm the platforms, captions and time with the user before calling this. TikTok choice (tiktokOptions): send it only when the user has told you, for THIS post, who can see it, whether comments, duets and stitches are allowed, and whether it promotes their own brand or is a paid partnership. You must pass privacyLevel explicitly — there is no default — and every other field too; nothing is filled in for you, and never copy a choice from another post, account or template. The server checks it against that TikTok account's current settings (audiences it offers, interactions the creator turned off, longest video it accepts) and refuses a choice that doesn't fit. With a choice the post goes straight to the profile at the scheduled time; by sending it you confirm the user agrees to TikTok's Music Usage Confirmation (and Branded Content Policy for a paid partnership). Without one the post waits in the TikTok queue (https://clipember.com/tiktok-queue) for the user to choose; if nobody does before the scheduled time, TikTok receives it as a draft in the user's TikTok Inbox to finish in the TikTok app. Say plainly to the user which TikTok posts wait for their choice. All posts of one call share a groupId (cancel them together with clipember_cancel_scheduled_post wholeGroup=true).

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": {
      "targets": "<targets>",
      "mode": "<mode>"
    },
    "name": "clipember_create_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYesschedule = at scheduledFor; now = within a minute; draft = save without queuing
clipIdNoA rendered clip — give this OR mediaId
tagIdsNoTags for the post (ids from clipember_list_tags)
mediaIdNoThe user's own video — give this OR clipId
targetsYes
signatureIdNoAppend this signature (id from clipember_list_signatures) to the end of every caption. Nothing is appended unless you pass it — not even the user's auto-add signature. Each network's caption limit counts the signature too.
scheduledForNoISO 8601, required for mode=schedule, e.g. 2026-12-01T14:00:00Z

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / targets / items / properties / platform / enum
      Previous value: -[
      -  "tiktok",
      -  "youtube_shorts",
      -  "instagram_reels",
      -  "bluesky",
      -  "facebook_reels",
      -  "threads",
      -  "linkedin"
      -]New value: +[
      +  "tiktok",
      +  "youtube_shorts",
      +  "instagram_reels",
      +  "bluesky",
      +  "facebook_reels",
      +  "threads",
      +  "linkedin",
      +  "pinterest"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / targets / items / properties / caption / description
      Previous value: -"Final text for this platform, exactly as it should appear (no AI text is added). Limits: TikTok 2200, YouTube description 5000, Instagram 2200."New value: +"Final text for this platform, exactly as it should appear (no AI text is added). Limits: TikTok 2200, YouTube description 5000, Instagram 2200, LinkedIn 3000, Bluesky 300."
    • changedInput schema / properties / targets / items / properties / settings / description
      Previous value: -"YouTube, Instagram, Bluesky, Facebook Reels or LinkedIn options. Not for TikTok (use tiktokOptions) or Threads (Threads takes only the caption, ≤500 characters)."New value: +"YouTube, Instagram, LinkedIn or Bluesky options. Not for TikTok (use tiktokOptions)."
  3. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only say it writes and is non-idempotent/open-world; the description goes much further, warning that YouTube Shorts and Instagram Reels publish publicly at the scheduled time, that server-side validation of the TikTok choice can refuse a call, and that an unset TikTok choice degrades to a queue then a TikTok Inbox draft. It also discloses that one call's posts share a groupId cancellable via clipember_cancel_scheduled_post wholeGroup=true — genuine behavior beyond structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and almost every clause carries information, but the body is a single dense paragraph of roughly 300 words with the TikTok queue/draft fallback, the Music Usage Confirmation consent, and a raw URL packed inline. It also restates schema-level facts ('every other field too; nothing is filled in for you', 'pass privacyLevel explicitly — there is no default') that the input schema already documents, so some sentences do not earn their place twice.

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 seven-parameter multi-platform publisher with open-world side effects and no output schema, this covers the source media, per-target requirements, validation failure modes, deferred TikTok queue behavior, and group cancellation. An agent could call it correctly and warn the user appropriately without further documentation.

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 86%, so the baseline is 3, but the description adds relational meaning the schema cannot express: one target per account, connectionId required only when a platform has multiple accounts, several accounts means multiple targets, and no TikTok field is ever inherited from another post. It also explains the consequence of each tiktokOptions choice against that account's current settings.

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 statement ('Schedule (or post now, or save as a draft) ONE video to several platforms at once'), and the three modes plus the mediaId/clipId source are named immediately. The scope ('ONE video', 'each target names its connectionId') is unambiguous. It does not, however, distinguish itself from the closely named sibling clipember_create_scheduled_post, which an agent could easily confuse with this tool.

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 strong conditional guidance: connections are required 'unless mode is draft', tiktokOptions is to be sent only when the user has specified visibility/interactions/brand status for THIS post, and omitting it deliberately routes the post to the TikTok queue. It also mandates confirming platforms, captions and time with the user before calling. Missing: any routing rule versus the sibling create/schedule tools.

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.

Resources