Skip to main content
Glama
Sign In

ShortSync

by app.shortsync
OverviewDiscussionsAdmin

Schedule post

schedule_post

Schedules an existing draft video post to publish at a specific future time. Typical flow: create_post_draft first, then schedule_post with the returned post's id. Pass scheduled_for (ISO 8601, at most 1 year out; past times are nudged to now + 30 seconds) or use_next_slot: true to take the next free saved posting time (see get_posting_slots). Pass recurrence to repeat the post on a cadence, like the app's "Repeat this post" (same shape as the public API).

Input Schema

NameRequiredDescriptionDefault
recurrenceNo"Repeat this post": publish the same post again on a cadence, like the app's Repeat option. scheduled_for is occurrence 1. Max 12 occurrences in total; each occurrence counts as one upload credit.
scheduled_forNoISO 8601 timestamp for when the post should publish. Max 1 year out. Required unless use_next_slot is true.
use_next_slotNoSchedule at the next free saved posting time for this workspace instead of scheduled_for. Fails when no posting times are saved (set them with update_posting_slots).
video_post_idYesThe video_posts.id to schedule. Typically obtained from create_post_draft.
idempotency_keyNoOptional client-generated key (e.g., a UUID) to make retries safe. Identical calls with the same key within 10 minutes return the original result instead of running the write twice.
notify_on_successNoEmail the user when the post successfully publishes. Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / recurrence
      Added value: +{
+  "description": "\"Repeat this post\": publish the same post again on a cadence, like the app's Repeat option. scheduled_for is occurrence 1. Max 12 occurrences in total; each occurrence counts as one upload credit.",
+  "properties": {
+    "count": {
+      "description": "Total occurrences including the first. Required when end_type is count.",
+      "maximum": 12,
+      "minimum": 2,
+      "type": "integer"
+    },
+    "end_date": {
+      "description": "Last day (YYYY-MM-DD, inclusive). Required when end_type is date.",
+      "type": "string"
+    },
+    "end_type": {
+      "description": "End after a number of occurrences (count) or on a date (end_date).",
+      "enum": [
+        "count",
+        "date"
+      ],
+      "type": "string"
+    },
+    "interval": {
+      "description": "Repeat every N units.",
+      "maximum": 12,
+      "minimum": 1,
+      "type": "integer"
+    },
+    "unit": {
+      "enum": [
+        "day",
+        "week",
+        "month"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "interval",
+    "unit",
+    "end_type"
+  ],
+  "type": "object"
+}
    • changedInput schema / properties / scheduled_for / description
      Previous value: -"ISO 8601 timestamp for when the post should publish. Max 1 year out."New value: +"ISO 8601 timestamp for when the post should publish. Max 1 year out. Required unless use_next_slot is true."
    • addedInput schema / properties / use_next_slot
      Added value: +{
+  "description": "Schedule at the next free saved posting time for this workspace instead of scheduled_for. Fails when no posting times are saved (set them with update_posting_slots).",
+  "type": "boolean"
+}
    • changedInput schema / required
      Previous value: -[
-  "video_post_id",
-  "scheduled_for"
-]New value: +[
+  "video_post_id"
+]
  2. First observed

TDQS

A5/5.0
Behavior5/5

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

The description provides crucial operational constraints not in the schema or annotations. It details the time limits (1 year out), the specific behavior for past times (nudged to now + 30 seconds), and links the recurrence shape to the public API.

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?

The structure is highly logical, following the flow from creation to scheduling options. It front-loads the core function and uses concise, technical language without unnecessary padding.

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?

Given the complexity of having multiple timing mechanisms (ISO, slot, recurrence) and requiring a prerequisite draft ID, the description successfully guides the agent through all necessary decision points.

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?

Although schema coverage is 100%, the description adds vital semantic meaning. It explains the logic behind the `scheduled_for` constraint and how the complex recurrence object relates to the app's 'Repeat this post' feature.

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?

The description clearly states that the tool schedules an existing draft video post. It distinguishes its function by specifying it targets 'draft video posts,' which is useful for distinguishing it from other post-creation or publishing tools in the sibling set.

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?

It provides a comprehensive workflow, explicitly stating that `create_post_draft` should typically be called first. Furthermore, it clarifies the three ways to define publication time: fixed ISO, using the next slot, or using recurrence.

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

All ShortSync toolsInspect
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