instagram-mcp-server

Publish Carousel

instagram_publish_carousel

Publishes 2-20 images or videos as one Instagram carousel post; creates child containers, waits for video processing, and counts it as a single post against the quota.

Instructions

Publish a carousel of 2-20 images and/or videos as one post.

This creates a child container per item, waits for any video children to process, then creates and publishes the carousel container. The whole carousel counts as a single post against the publishing quota.

Example: "post these three photos as one post" -> items=[{image_url:"..."},{image_url:"..."},{image_url:"..."}]

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

Input Schema

Name	Required	Description
`items`	Yes	Ordered carousel items, 2-20 of them
`caption`	No	Caption text, up to 2200 characters. Hashtags and @mentions work inside the caption. Instagram counts a maximum of 30 hashtags.
`account_id`	No	Instagram professional account ID. Omit to use the token's own account.
`location_id`	No	Facebook Page ID of a location to tag
`wait_seconds`	No	Seconds to wait for video processing before giving up and returning the container ID. 0 publishes immediately (images only). Default 60.
`collaborators`	No	Up to 3 collaborator usernames
`is_ai_generated`	No	Mark the carousel as AI-generated

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare it as an open-world, non-idempotent, non-read-only mutation. The description adds real context beyond that: the internal sequence (child container per item, wait for video processing, then carousel container), the quota accounting (whole carousel counts as one post), and the give-up behavior of wait_seconds. Missing is any statement of permission/token requirements for publishing to another account.

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?

Front-loaded one-sentence purpose, then a short mechanics paragraph, then a compact example. Every sentence carries information about limits, sequencing, or quota; nothing is redundant.

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 7-parameter publishing tool with full schema coverage and annotations, the definition covers purpose, sequencing, quota impact, and video-processing behavior. The notable gap is that with no output schema, the definition never says what a successful publish returns (media ID vs container ID), which matters for follow-up calls.

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 100%, so the baseline would be 3, but the worked example concretely maps a natural-language request onto the items array shape, which is genuine added meaning for the one required parameter. The remaining six parameters are not touched in the description, relying entirely on the schema.

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?

States a specific verb (publish) plus resource (carousel) and fixes the scope precisely: 2-20 images and/or videos combined into one post. That scope alone separates it from the single-item siblings like instagram_publish_image and instagram_publish_reel without needing to name them.

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 usage guidance is delivered by example ("post these three photos as one post" -> items=[...]), which implies when to reach for this tool rather than a single-image publish. There is no explicit when-not guidance and no statement of what to do when only one item exists, leaving that routing to inference.

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

Deploy Server