instagram-mcp

publish_carousel

Publish a multi-image carousel to Instagram with 2-10 images using public HTTPS URLs. Creates child containers for each image and a carousel parent post.

Instructions

Publish a multi-image carousel (2-10 images). Each image_url must be a PUBLIC https URL.

Creates one child container per image (is_carousel_item) then a CAROUSEL parent, then publishes.

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": {
      "image_urls": "<image_urls>"
    },
    "name": "publish_carousel"
  }
}

Input Schema

Name	Required	Description	Default
`account`	No
`caption`	No
`image_urls`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Jul 29, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses the multi-step creation flow: child containers per image marked is_carousel_item, then a CAROUSEL parent, then publishing. It also communicates the public-https constraint. It does not detail irreversible side effects or failure modes, but the core behavior is transparent.

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 compact and front-loaded: the first sentence states purpose and constraint, the second explains the internal flow. Every sentence adds value and there is no redundant wording.

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-value details are not required. Still, the description omits meaningful invocation context: what the account parameter controls when omitted, whether caption is a per-carousel caption, and how publishing limits apply. These gaps matter for an agent choosing between this and sibling publish tools.

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 0%, so the description must compensate. It enriches image_urls with the 2-10 range and public-URL requirement, but leaves account and caption semantically unexplained. The required parameter is well covered, while optional parameters rely on name inference.

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 'Publish a multi-image carousel (2-10 images)', which names a specific verb, resource, and numeric constraint. It clearly differentiates this tool from sibling single-media publishers like publish_image, publish_video, publish_reel, and publish_story.

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 clearly implies this tool is for multi-image carousels and not for other media types, and it adds a public-URL requirement. However, it does not explicitly name alternative tools or state 'use publish_image for a single image', so there is clear context but no formal exclusions.

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