Skip to main content
Glama
Instagram Campaign MCP

Instagram Campaign MCP

by enimarix

publish_reel

Publishes a Reel to Instagram from a public HTTPS video URL or media-root file, with caption, collaborators, cover, feed sharing, and trial Reel graduation.

Instructions

Publish a Reel now (MP4/MOV H.264+AAC, 9:16 recommended, max 300 MB). Give exactly one of video_url (public HTTPS) or video_path (file relative to the media root; a studio asset's video is refused: queue it from the website). trial_graduation makes it a trial Reel shown to non-followers first: SS_PERFORMANCE = Instagram shares it to followers if it performs, MANUAL = you decide in the app. Waits for video processing (can take minutes).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "publish_reel"
  }
}

Input Schema

NameRequiredDescriptionDefault
captionNo
variantNo
campaignNo
cover_urlNo
video_urlNo
audio_nameNo
hypothesisNo
video_pathNo
collaboratorsNo
share_to_feedNo
thumb_offset_msNo
trial_graduationNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations cover the safety profile (not read-only, not idempotent, open-world), and the description adds genuinely new operational behavior: the call blocks while the video is processed and can take minutes, exactly one of two video sources must be supplied, and a specific input class is hard-refused. It does not address auth/permission requirements or what happens if the same video is published twice (relevant given idempotentHint=false).

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?

The verb and the hard constraints are front-loaded, and the parenthetical format spec is an efficient way to pack validation rules into one clause. It is dense but nearly every clause carries a fact the agent needs; only the phrasing is slightly compressed for the volume of information.

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?

Because an output schema exists, the lack of return-value discussion is acceptable, and the blocking behavior plus the video-source rule cover the highest-risk failure modes. However, for a 12-parameter publishing mutation with zero schema documentation, most inputs remain unexplained, leaving the definition incomplete for correct invocation on anything beyond the video source.

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 12 parameters, so the description carries the full burden, yet it only explains video_url, video_path, and the two trial_graduation values. Nine parameters — caption, variant, campaign, cover_url, audio_name, hypothesis, collaborators, share_to_feed, thumb_offset_ms — are left with bare names; domain terms like "variant", "hypothesis", and "campaign" are especially opaque without any indication that they are experiment-tracking metadata.

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?

"Publish a Reel now" is a specific verb plus a specific resource, and the media type alone distinguishes it from publish_carousel, publish_image, and publish_story without requiring the agent to open another schema. The added format envelope (MP4/MOV H.264+AAC, 9:16, max 300 MB) further pins down exactly what this tool accepts.

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?

It gives a concrete exclusion with a redirect: a studio asset's video_path is refused and must be queued from the website instead. It also explains the two trial_graduation modes so the agent can choose between them. What's missing is routing guidance against schedule_post for deferred publishing, which the agent must infer from the word "now".

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