Skip to main content
Glama

Schedule Post

autoposter_schedule_post
Destructive

Schedules a post for a future date/time. Automatically converts local time using workspace/user timezone into UTC. Accepts mediaUrls (public URLs) or files (client-supplied file objects 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.

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": {
      "accountIds": "<accountIds>",
      "content": "<content>",
      "scheduledAt": "<scheduledAt>"
    },
    "name": "autoposter_schedule_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesNoOptional client-supplied file objects to attach to the post.
titleNoOptional title. Used by YouTube, Pinterest and WordPress; ignored elsewhere.
contentYesBase text content of the post.
mediaIdsNoOptional list of existing media IDs from workspace media library (from autoposter_list_media).
postTypeNoOptional target format where applicable: 'post' (default feed post/carousel), 'reel' (Instagram or Facebook Reel; requires video), 'story' (Instagram or Facebook 24h Story; requires image or video), or 'shorts' (YouTube Shorts; vertical video under 60s). Ignored on platforms without format variants.
timezoneNoOptional IANA timezone (e.g. 'America/New_York'). If omitted, defaults to workspace or user timezone.
mediaUrlsNoOptional public image or video URLs to attach (e.g. from autoposter_upload_media).
accountIdsYesList of account IDs from autoposter_list_accounts.
visibilityNoOptional audience for TikTok posts (default PUBLIC_TO_EVERYONE). Ignored on other platforms.
scheduledAtYesScheduled ISO timestamp or local datetime string, e.g. '2026-10-05T14:00:00'.
firstCommentNoOptional first comment posted on the post right after it publishes (e.g. links or hashtags). Supported on platforms with comment support such as X, Facebook, Instagram, LinkedIn, Threads, Bluesky, Mastodon, Telegram, Discord.
threadCommentsNoOptional thread: follow-up texts posted in order after publishing, each replying to the previous one. If firstComment is also set, these come after it. On X this makes a tweet thread.
platformContentNoOptional platform-specific content overrides (e.g. twitter, linkedin).

Output Schema

NameRequiredDescriptionDefault
statusYesStatus of the scheduled post ('scheduled' or 'pending_approval').
messageNoStatus message.
successYesWhether the post was successfully scheduled.
timezoneNoTimezone applied.
scheduledAtYesScheduled time in UTC.
scheduledPostsYesList of scheduled posts per target account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / firstComment
      Added value: +{
      +  "description": "Optional first comment posted on the post right after it publishes (e.g. links or hashtags). Supported on platforms with comment support such as X, Facebook, Instagram, LinkedIn, Threads, Bluesky, Mastodon, Telegram, Discord.",
      +  "type": "string"
      +}
    • addedInput schema / properties / threadComments
      Added value: +{
      +  "description": "Optional thread: follow-up texts posted in order after publishing, each replying to the previous one. If firstComment is also set, these come after it. On X this makes a tweet thread.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / title
      Added value: +{
      +  "description": "Optional title. Used by YouTube, Pinterest and WordPress; ignored elsewhere.",
      +  "type": "string"
      +}
    • addedInput schema / properties / visibility
      Added value: +{
      +  "description": "Optional audience for TikTok posts (default PUBLIC_TO_EVERYONE). Ignored on other platforms.",
      +  "enum": [
      +    "PUBLIC_TO_EVERYONE",
      +    "SELF_ONLY",
      +    "MUTUAL_FOLLOW_FRIENDS"
      +  ],
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / files / description
      Previous value: -"Optional files generated in chat or uploaded by user to attach to the post."New value: +"Optional client-supplied file objects to attach to the post."
  3. Changed1 schema field changed
    • addedInput schema / properties / platformContent / additionalProperties
      Added value: +{
      +  "type": "string"
      +}
  4. Changed2 schema fields changed
    • addedInput schema / properties / postType
      Added value: +{
      +  "description": "Optional target format where applicable: 'post' (default feed post/carousel), 'reel' (Instagram or Facebook Reel; requires video), 'story' (Instagram or Facebook 24h Story; requires image or video), or 'shorts' (YouTube Shorts; vertical video under 60s). Ignored on platforms without format variants.",
      +  "enum": [
      +    "post",
      +    "reel",
      +    "story",
      +    "shorts"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / scheduledPosts / items / properties / postType
      Added value: +{
      +  "description": "Target format ('post', 'reel', 'story', or 'shorts').",
      +  "type": "string"
      +}
  5. Changed1 schema field changed
    • 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"
      +}
  6. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=true, openWorld=true, so the safety profile is partly covered. The description adds genuinely non-obvious behavior: automatic timezone-to-UTC conversion, the 100MB file ceiling, and the public-URL requirement. It omits that scheduled posts can later be cancelled via autoposter_delete_post and says nothing about validation failures or per-platform limits.

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?

Four short sentences, front-loaded with the core action and the timezone behavior, then the media constraints, then the escalation path for large files. Nothing is repeated from the schema and no sentence is filler.

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?

For a 13-parameter, nested-object, open-world mutation tool the description covers the high-risk bits (timing semantics, media sourcing, size cap, escape hatch). An output schema exists, so return values need not be explained. Minor residual gap: no mention of what happens on partial failure across multiple accountIds.

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 a 3 is the baseline; the description earns a bump by clarifying the three-way media input choice (mediaUrls public URLs vs. client-supplied files vs. mediaIds) and by explaining timezone defaulting when omitted. It still leaves the precedence/conflict behavior between mediaUrls, files, and mediaIds unstated.

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 with timing scope: 'Schedules a post for a future date/time.' That cleanly separates it from immediate publish/cancel siblings. It does not, however, contrast itself with autoposter_draft_post or autoposter_update_post, which are the nearest confusable neighbors.

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 a clear conditional routing rule for oversized video ('tell the user to provide a direct public file URL or use autoposter_get_media_upload_url'), and implicitly frames this as the tool for the scheduled (not draft) path. It stops short of explicit when-not guidance, e.g. it never says to use autoposter_draft_post when no publish time is known.

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