Instagram MCP Server

publish_carousel

Publish a carousel post to Instagram by providing 2-10 public image URLs and an optional caption. Handles creation and posting of all child containers automatically.

Instructions

Publish a carousel (multi-image) post. Accepts 2-10 images.

THIS IS A WRITE OPERATION. Each image must be publicly accessible. Creates a child container per image, then a carousel container, then publishes. Slow — expect 30-60s.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`caption`	No	Caption applied to the whole carousel
`image_urls`	Yes	2-10 PUBLIC image URLs. Must all be accessible JPEGs.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 16, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With no annotations, the description fully bears the burden. It explicitly states 'THIS IS A WRITE OPERATION', details the internal sequence (child containers then carousel container then publish), and warns about slowness (30-60s). This is comprehensive for a creation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is four efficient sentences with no wasted words. Each sentence serves a clear purpose: function, operation type, requirements, and behavioral note. Front-loaded with purpose.

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?

Given the presence of an output schema (handling return values) and only two parameters, the description covers all essential aspects: what the tool does, prerequisites, and performance expectations. It is complete for its complexity.

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

Parameters3/5

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

Schema description coverage is 100%, so baseline 3. The description adds little beyond the schema: it repeats '2-10 images' and accessibility requirement (already in schema). The internal process detail does not enhance parameter meaning. Thus, score 3.

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 clearly states 'Publish a carousel (multi-image) post.' The verb 'Publish' and resource 'carousel post' are specific, and it distinguishes itself from single-image (publish_photo) and video (publish_reel) siblings.

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?

The description gives prerequisites (publicly accessible images, 2-10 images) and a timing warning. However, it does not explicitly tell the agent when to choose this tool over alternatives like publish_photo or publish_reel, though it is implied for multi-image posts.

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