Skip to main content
Glama

schedule_post

Schedule (or publish now) a photo post or a carousel post.

One URL in image_urls makes a single photo post; 2-10 make a carousel, posted in the order given. Each URL must be publicly fetchable — a direct link to the file itself, the same rule schedule_reel's source_url follows. Images and videos are both allowed in a carousel; each item's type is detected when it's downloaded.

Instead of image_urls, carousel_id posts an AI carousel made in reeldrop, slides in order (every slide must have its image). Pass one or the other.

Timing: exactly one of scheduled_at (a future, timezone-aware ISO datetime — get real slots from get_posting_slots rather than guessing) or publish_now=true. Omit both to save a draft the user can finish in reeldrop.

caption is required — ask the user for it, or draft options with generate_reel_captions and let them pick; never invent one and post it. Up to 5 hashtags. first_comment is posted right after publishing (Creator plan). automation_id attaches a comment-to-DM automation to the post once it's live.

For a reel use schedule_reel; for a story use publish_story (now) or schedule_story (later).

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": {
      "workspace_id": "<workspace_id>",
      "ig_account_id": "<ig_account_id>"
    },
    "name": "schedule_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
captionNo
hashtagsNo
image_urlsNo
carousel_idNo
publish_nowNo
client_tokenNo
scheduled_atNo
workspace_idYes
automation_idNo
first_commentNo
ig_account_idYes

Output Schema

NameRequiredDescriptionDefault
modeYes
statusYes
post_idYes
scheduled_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / caption / default
      Added value: +""
    • addedInput schema / properties / carousel_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
    • addedInput schema / properties / image_urls / anyOf
      Added value: +[
      +  {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / image_urls / default
      Added value: +null
    • removedInput schema / properties / image_urls / items
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / image_urls / type
      Removed value: -"array"
    • changedInput schema / required
      Previous value: -[
      -  "workspace_id",
      -  "ig_account_id",
      -  "image_urls",
      -  "caption"
      -]New value: +[
      +  "workspace_id",
      +  "ig_account_id"
      +]
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the supplied annotations: it discloses that URLs must be publicly fetchable direct file links, that item type is detected at download time, that carousel items post in the order given, and that first_comment requires the Creator plan. The draft fallback when no timing is supplied is real behavioral context an agent could not infer from readOnlyHint/openWorldHint alone.

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 purpose and mode selection, then broken into focused paragraphs for media source, timing, and caption/automation concerns. Dense but nearly every sentence carries a constraint; only the 'images and videos are both allowed' clause feels like a minor aside.

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 an 11-parameter mutation tool this covers what an agent needs: media source rules, mutual exclusivity, timing modes, draft behavior, caption requirement, and plan-gated fields. With an output schema present, it correctly avoids explaining return values and spends its length on invocation semantics instead.

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?

With 0% schema description coverage the description carries the burden, and it defines the non-obvious semantics of nearly every functional parameter: image_urls cardinality (1 vs 2-10) and ordering, carousel_id exclusivity, timezone-aware future ISO for scheduled_at, and the up-to-5 limit on hashtags. It leaves workspace_id, ig_account_id, and especially client_token (an idempotency token) unexplained, which is the only real gap.

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 concrete verb and resource ('Schedule (or publish now) a photo post or a carousel post'), which immediately separates it from reel and story posting. The closing sentence names the exact siblings to use for those other media types, so an agent can route without opening any 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?

Explicitly states when to use this tool versus schedule_reel, publish_story, and schedule_story, and gives hard selection rules inside the tool: pass image_urls OR carousel_id, and exactly one of scheduled_at or publish_now, or omit both for a draft. It also directs the agent to get_posting_slots instead of guessing a timestamp, which is a genuine when-to-use constraint.

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