Skip to main content
Glama

schedule_reels_bulk

Schedule (or immediately publish) multiple Instagram reels in one call — e.g. every video in a Google Drive folder. Each item is independent: one item failing (a bad URL, an oversized file, a quota miss) does not abort the rest of the batch. See schedule_reel for what each item needs — one of source_url/video_token, one of scheduled_at/publish_now, and (same as schedule_reel) a non-blank caption, at least one hashtag, and a cover_choice of "instagram_default" or "custom" — generate a caption per video with generate_reel_captions and confirm the cover choice with the user before calling this, rather than batch-scheduling any of them caption-less or with the thumbnail decided silently. Retrying an identical batch is safe — items without an explicit client_token get one derived from (ig_account_id, source_url-or- video_token, scheduled_at-or-publish_now), so retried items resolve to the post already created rather than a duplicate.

Accepts at most 15 items per call — split a larger batch into several calls.

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>",
      "items": "<items>"
    },
    "name": "schedule_reels_bulk"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
workspace_idYes
max_concurrencyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations, it discloses the key behavioral facts: per-item independence (a bad URL, oversized file, or quota miss does not abort the batch) and retry semantics via a derived client_token from (ig_account_id, source_url-or-video_token, scheduled_at-or-publish_now). That retry-safety claim sits in mild tension with idempotentHint=false, but it reads as added nuance about dedupe keys rather than a direct inversion of the annotation, so no contradiction is flagged. It could still say more about whether failures are reported per item and how partial results are surfaced.

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 the action and the batch-isolation guarantee, then prerequisites, then the retry note and the 15-item cap — a sensible priority order. It is dense but nearly every sentence carries an actionable constraint; the awkward line wrapping makes it slightly harder to scan than it needs to be.

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 mutation tool with an output schema, it covers the essentials an agent needs to call correctly: per-item requirements, failure isolation, retry safety, and the batch size ceiling. The remaining gap is small — a one-line note on max_concurrency and the trial-reel flags would close it 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?

Schema description coverage is 0%, so the description must carry the load, and it does for the consequential fields: source_url-vs-video_token, scheduled_at-vs-publish_now, non-blank caption, at least one hashtag, the cover_choice values ('instagram_default' or 'custom'), and the client_token derivation rule. It leaves trial_reel, trial_graduation, share_to_feed, automation_id, and max_concurrency (including its default of 3) unexplained, which keeps it short of a 5.

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 opens with a concrete verb and resource — 'Schedule (or immediately publish) multiple Instagram reels in one call' — and gives a worked example (every video in a Google Drive folder). It also implicitly distinguishes itself from the singular sibling by pointing to schedule_reel for per-item requirements, so an agent can tell bulk from single-item scheduling without opening either 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?

It routes the agent explicitly: use generate_reel_captions to produce captions and confirm the cover choice with the user before calling, and don't batch-schedule caption-less items or silently decided thumbnails. It also states a hard operational boundary — split batches larger than 15 items into several calls — which is exactly the kind of when/when-not guidance that prevents misuse.

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