AutoPoster AI

Schedule Post

autoposter_schedule_post

Schedules a post for a future date/time. Automatically converts local time using workspace/user timezone into UTC. Accepts mediaUrls (public URLs) or files (AI-generated images or uploaded files from chat up to 100MB). For large video files over 100MB, tell the user to provide a direct public file URL or use autoposter_get_media_upload_url.

Input Schema

TableJSON Schema

Name	Required	Description
`files`	No	Optional files generated in chat or uploaded by user to attach to the post.
`content`	Yes	Base text content of the post.
`mediaIds`	No	Optional list of existing media IDs from workspace media library (from autoposter_list_media).
`timezone`	No	Optional IANA timezone (e.g. 'America/New_York'). If omitted, defaults to workspace or user timezone.
`mediaUrls`	No	Optional public image or video URLs to attach (e.g. from autoposter_upload_media).
`accountIds`	Yes	List of account IDs from autoposter_list_accounts.
`scheduledAt`	Yes	Scheduled ISO timestamp or local datetime string, e.g. '2026-10-05T14:00:00'.
`platformContent`	No	Optional platform-specific content overrides (e.g. twitter, linkedin).

Output Schema

TableJSON Schema

Name	Required	Description
`status`	Yes	Status of the scheduled post ('scheduled' or 'pending_approval').
`message`	No	Status message.
`success`	Yes	Whether the post was successfully scheduled.
`timezone`	No	Timezone applied.
`scheduledAt`	Yes	Scheduled time in UTC.
`scheduledPosts`	Yes	List of scheduled posts per target account.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "message": {
+      "description": "Status message.",
+      "type": "string"
+    },
+    "scheduledAt": {
+      "description": "Scheduled time in UTC.",
+      "type": "string"
+    },
+    "scheduledPosts": {
+      "description": "List of scheduled posts per target account.",
+      "items": {
+        "properties": {
+          "accountName": {
+            "description": "Target account name.",
+            "type": "string"
+          },
+          "id": {
+            "description": "Post ID.",
+            "type": "string"
+          },
+          "platform": {
+            "description": "Target platform.",
+            "type": "string"
+          },
+          "scheduledAt": {
+            "description": "Scheduled timestamp.",
+            "type": "string"
+          },
+          "status": {
+            "description": "Post status.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "platform",
+          "status",
+          "scheduledAt"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "status": {
+      "description": "Status of the scheduled post ('scheduled' or 'pending_approval').",
+      "type": "string"
+    },
+    "success": {
+      "description": "Whether the post was successfully scheduled.",
+      "type": "boolean"
+    },
+    "timezone": {
+      "description": "Timezone applied.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "success",
+    "status",
+    "scheduledAt",
+    "scheduledPosts"
+  ],
+  "type": "object"
+}

First observedOct 7, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnly=false, destructive=false, openWorld=true), so the description's added context is what counts: automatic local-to-UTC timezone conversion and the 100MB media size ceiling are genuine behavioral disclosures beyond the annotations.

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?

Three sentences, each front-loaded with the operative fact (schedule, timezone conversion, media handling) and no filler. The media sentence is dense but each clause adds distinct rules.

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?

An output schema exists, so return values need not be described. The description covers the non-obvious essentials (timezone handling, media sourcing, size limit), leaving only minor gaps such as multi-account behavior and scheduling-window constraints.

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. The description goes further by explaining that timezone is auto-resolved from workspace/user defaults and that files/mediaUrls carry a concrete 100MB limit, adding constraint semantics the schema alone does not convey.

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?

States a specific verb and resource ('Schedules a post for a future date/time') with clear temporal scope. It is distinguishable from siblings like autoposter_draft_post and autoposter_publish_draft by the 'future date/time' framing, though it never names an alternative to contrast against explicitly.

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 actionable routing guidance: use mediaUrls for public URLs, files for AI-generated/uploads under 100MB, and redirect large videos to a public URL or autoposter_get_media_upload_url. It does not, however, clarify when to schedule vs. draft or publish immediately.

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

All AutoPoster AI tools Inspect

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

Need Help?