Skip to main content
Glama

schedule_reel

Schedule, or immediately publish, a single Instagram reel.

Provide exactly one of source_url or video_token: source_url is a direct, publicly-fetchable link to the video file itself — e.g. a Google Drive file's webContentLink with the file shared as "Anyone with the link". Do NOT pass base64 file content here (for example from a Drive connector's download_file_content tool) — this tool downloads the video server-side from the URL you provide. video_token is the value generate_reel_captions returned for a video already uploaded through that tool — pass it here to reuse that upload instead of re-fetching source_url.

Provide exactly one of scheduled_at (a timezone-aware datetime in the future) or publish_now=true. publish_now sends the reel straight into the publish pipeline instead of scheduling it for later — the result's status will be "publishing", not "scheduled", since it isn't confirmed live on Instagram yet when this call returns.

caption and hashtags are both required — this tool refuses a blank caption or an empty hashtags list rather than posting one silently. If you don't already have a caption for this video, call generate_reel_captions first (same source_url/video_token), show the user all 3 options, and let them pick — or ask whether they'd rather you choose — then retry this call with that caption and its recommended_hashtags.

cover_choice is also required, and must be exactly "instagram_default" (Instagram auto-generates the cover — leave cover_url unset) or "custom" (you're supplying a specific image — cover_url must then be a public URL, or upload one via get_video_upload_url if it's local). Ask the user which they want; don't decide silently. There's no third "use the video's first frame" option — reeldrop has no way to extract one, and instagram_default is the closest available equivalent.

automation_id (optional) links a DM/comment automation that was created with post_target="attach_later" (create_automation) to this reel the moment it's scheduled — the one-call version of what would otherwise take a follow-up update_scheduled_post call.

trial_reel=true publishes it as an Instagram trial reel: shown to non-followers first, kept off the profile grid until it is shared with followers. trial_graduation decides how that sharing happens: "MANUAL" (the default; the user shares it from the Instagram app when they choose) or "SS_PERFORMANCE" (Instagram shares it automatically if it performs well). Ask the user which they want. No API can share a trial reel to followers later, so reeldrop can't do it for them. A trial reel uses the plan's monthly trial-reel allowance (get_plan_usage). Track it with get_trial_reel_analytics.

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_reel"
  }
}

Input Schema

NameRequiredDescriptionDefault
captionNo
hashtagsNo
cover_urlNo
source_urlNo
trial_reelNo
publish_nowNo
video_tokenNo
client_tokenNo
cover_choiceNo
scheduled_atNo
workspace_idYes
automation_idNo
ig_account_idYes
share_to_feedNo
allow_commentsNo
allow_remixingNo
trial_graduationNo

Output Schema

NameRequiredDescriptionDefault
errorNo
indexNo
statusYes
post_idNo
source_urlNo
scheduled_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare this as a non-read-only, non-idempotent, open-world write. The description goes well beyond: it discloses that publish_now returns status "publishing" rather than "scheduled", that blank captions and empty hashtag lists are rejected, that trial reels consume a monthly allowance and cannot be auto-shared later by any API, and that exactly-one-of constraints apply to two parameter pairs.

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?

Roughly 450 words, but front-loaded with the core action and then organized into per-parameter blocks with the highest-risk constraints called out first. A few asides, such as the explanation that no first-frame cover option exists, are long-winded yet serve as real guardrails against a plausible wrong call.

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 17-parameter write tool with an output schema, the description covers every decision the agent must resolve before calling: video source, timing mode, caption/hashtag prerequisite, cover policy, automation linkage, and trial-reel mode. Return-value detail is correctly left to the output schema, with only the non-obvious status semantics spelled out.

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 full burden, and it does well: it defines source_url vs video_token mutual exclusivity and provenance, scheduled_at vs publish_now, cover_choice's two valid values and how cover_url pairs with them, automation_id's link-to-attach_later semantics, and trial_graduation's MANUAL vs SS_PERFORMANCE meanings. It leaves workspace_id, ig_account_id, client_token, share_to_feed, allow_comments, and allow_remixing undefined — client_token is the notable miss given idempotentHint=false and the risk of duplicate publishes.

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-plus-resource statement: schedule or immediately publish a single Instagram reel. That distinguishes it from siblings like schedule_reels_bulk, schedule_post, schedule_story, and update_scheduled_post without the agent needing 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 routing rules throughout: call generate_reel_captions first if no caption exists and show the user all 3 options, use get_video_upload_url for local cover images, use update_scheduled_post as the alternative to automation_id, and track trial-reel allowance via get_plan_usage. It also names what not to do (no base64 in source_url, no silent blank caption).

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