Skip to main content
Glama

Queue a clip for publishing

clipember_create_scheduled_post

Queue a rendered clip to publish to a platform at a given time. For youtube_shorts and instagram_reels this WILL post publicly to the connected account when the time arrives — confirm with the user before calling this. For tiktok: 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. Pass a scheduledFor of right now (or a few seconds out) to act immediately — for a tiktok post without tiktokOptions that leaves no time to choose, so it lands in the Inbox. The platform must already be connected (clipember_list_platform_connections); if it has several connected accounts, pass connectionId to pick one. Prefer clipember_create_post.

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": {
      "clipId": "<clipId>",
      "platform": "<platform>",
      "scheduledFor": "<scheduledFor>"
    },
    "name": "clipember_create_scheduled_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipIdYes
platformYes
connectionIdNoWhich account (id from clipember_list_platform_connections) — required when the platform has several connected accounts
scheduledForYesISO 8601 datetime, e.g. 2026-08-10T14:00:00Z
tiktokOptionsNotiktok only: the TikTok choice for this post, every field required (title = the caption, required here). Leave it out and the post waits in the TikTok queue.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / 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. Changed3 schema fields changed
    • addedInput schema / properties / connectionId
      Added value: +{
      +  "description": "Which account (id from clipember_list_platform_connections) — required when the platform has several connected accounts",
      +  "format": "uuid",
      +  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      +  "type": "string"
      +}
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "tiktok",
      -  "youtube_shorts",
      -  "instagram_reels"
      -]New value: +[
      +  "tiktok",
      +  "youtube_shorts",
      +  "instagram_reels",
      +  "bluesky",
      +  "facebook_reels",
      +  "threads",
      +  "linkedin"
      +]
    • addedInput schema / properties / tiktokOptions
      Added value: +{
      +  "description": "tiktok only: the TikTok choice for this post, every field required (title = the caption, required here). Leave it out and the post waits in the TikTok queue.",
      +  "properties": {
      +    "brandContentToggle": {
      +      "description": "REQUIRED. Commercial content disclosure, \"Branded content\": true for a paid partnership with a third party. Can't be combined with SELF_ONLY. Both disclosure flags false = the video promotes nothing.",
      +      "type": "boolean"
      +    },
      +    "brandOrganicToggle": {
      +      "description": "REQUIRED. Commercial content disclosure, \"Your brand\": true when the video promotes the user's own business.",
      +      "type": "boolean"
      +    },
      +    "disableComment": {
      +      "description": "REQUIRED. true = comments off. Can't be false if the creator turned comments off in TikTok.",
      +      "type": "boolean"
      +    },
      +    "disableDuet": {
      +      "description": "REQUIRED. true = duets off. Can't be false if the creator turned duets off in TikTok.",
      +      "type": "boolean"
      +    },
      +    "disableStitch": {
      +      "description": "REQUIRED. true = stitches off. Can't be false if the creator turned stitches off in TikTok.",
      +      "type": "boolean"
      +    },
      +    "privacyLevel": {
      +      "description": "Who can see the video. REQUIRED, there is no default — ask the user. PUBLIC_TO_EVERYONE = everyone, MUTUAL_FOLLOW_FRIENDS = friends (people they follow back), FOLLOWER_OF_CREATOR = followers, SELF_ONLY = only them. It must be one the account offers right now — otherwise the call is refused and the error lists the ones it offers.",
      +      "enum": [
      +        "PUBLIC_TO_EVERYONE",
      +        "MUTUAL_FOLLOW_FRIENDS",
      +        "FOLLOWER_OF_CREATOR",
      +        "SELF_ONLY"
      +      ],
      +      "type": "string"
      +    },
      +    "title": {
      +      "description": "The TikTok caption. Left out: this target's caption is used — one of the two must be non-empty.",
      +      "maxLength": 2200,
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "privacyLevel",
      +    "disableComment",
      +    "disableDuet",
      +    "disableStitch",
      +    "brandOrganicToggle",
      +    "brandContentToggle"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes far beyond the annotations: it discloses that the post goes live publicly on YouTube/Instagram, that the server validates TikTok choices against the account's current settings and refuses mismatches, that sending tiktokOptions constitutes agreement to TikTok's Music Usage Confirmation and Branded Content Policy, and the two fallback paths (queue, then Inbox draft). The annotations only say non-read-only, open-world, non-idempotent — the description supplies the real consequences.

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 action and consequence, then progressively drills into TikTok specifics. It is a single dense block that runs long, and the TikTok fallback explanation is repeated in slightly different phrasing, but nearly every sentence carries operative information.

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 5-parameter tool with a nested object, no output schema, and real-world side effects, the description covers prerequisites, per-platform divergence, validation failure modes, and the consequences of omitting optional parameters. Nothing an agent needs to call it safely is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds meaning the schema cannot: privacyLevel has no default and must be asked of the user, all tiktokOptions fields are mandatory with nothing filled in, choices must not be copied from another post/account/template, and connectionId is only needed when several accounts are connected. This compensates for the 60% schema coverage and makes the nested object usable.

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+resource+scope: "Queue a rendered clip to publish to a platform at a given time." It closes by routing to the sibling alternative ("Prefer clipember_create_post"), so an agent can distinguish queued/scheduled publishing from immediate post creation without opening the schema.

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?

Explicit when-to-use and when-not-to-act guidance: confirm with the user before calling for youtube_shorts/instagram_reels because it posts publicly, and only send tiktokOptions when the user has supplied every choice for THIS post. It also states prerequisites (the platform must be connected via clipember_list_platform_connections, pass connectionId when multiple accounts exist) and the immediate-publish shortcut (scheduledFor = now).

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