Skip to main content
Glama
Instagram Campaign MCP

Instagram Campaign MCP

by enimarix

schedule_post

Queue an Instagram post for a future time by setting the content type and ISO 8601 publish date, then let the scheduler run it automatically.

Instructions

Queue a post for later. A reel takes video_url or video_path (relative to the media root; a studio asset's video is refused). publish_at is ISO 8601; without an offset it is read in the configured time zone (default Europe/Paris), e.g. "2026-11-20T18:30". Needs the scheduler running (python -m src.scheduler daemon) or run_due_posts.

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": {
      "kind": "<kind>",
      "publish_at": "<publish_at>"
    },
    "name": "schedule_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
itemsNo
captionNo
variantNo
alt_textNo
campaignNo
cover_urlNo
image_urlNo
video_urlNo
hypothesisNo
publish_atYes
video_pathNo
collaboratorsNo
share_to_feedNo
trial_graduationNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations only declare it is a non-destructive, non-open-world write. The description adds real operational context beyond that: media-path resolution relative to a media root, refusal of studio-asset videos, ISO 8601 parsing with a default Europe/Paris zone, and the requirement for a running scheduler. It does not say what happens on validation failure or what the tool returns, but the added constraints are substantial.

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, front-loaded with the action, then constraints, then the operational prerequisite. It is dense and mostly waste-free, though the emphasis is heavily skewed toward reel-specific behavior while kind accepts four enum values.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 explained. But for a 15-parameter tool with zero schema descriptions, the definition covers only a small fraction of what an agent needs to construct a valid call, particularly which parameters each kind requires.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 15 parameters, so the description must carry the load and it only explains two of them: video_url/video_path for reels and publish_at's format and timezone. Everything else (items, caption, variant, alt_text, campaign, cover_url, image_url, hypothesis, collaborators, share_to_feed, trial_graduation) is left entirely undocumented.

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?

"Queue a post for later" gives a specific verb plus resource and implicitly contrasts with the immediate publish_* siblings. It does not name any sibling explicitly, so an agent must infer the boundary between scheduling and publishing, but the intent is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description names a concrete prerequisite (scheduler daemon must be running, or use run_due_posts) which is genuine when-to-use context. However, it never states when to prefer schedule_post over publish_reel/publish_image/publish_story, nor when reschedule_post or cancel_scheduled_post apply.

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