instagram-mcp

post_carousel

Post a carousel of up to 10 photos or videos to Instagram by supplying media URLs and an optional caption via the Instagram Graph API.

Instructions

Dang carousel (nhieu anh/video, toi da 10) len Instagram.

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": "post_carousel"
  }
}

Input Schema

Name	Required	Description	Default
`items`	Yes	Danh sach item: moi item co image_url HOAC video_url
`caption`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 4, 2026

TDQS

B3.4/5.0

Behavior3/5

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

There are no annotations, so the description carries the burden. It discloses a key constraint: maximum 10 items. However, it does not mention other behavioral aspects like whether the post publishes immediately, authentication requirements, or possible side effects. The 'max 10' is useful but limited.

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 a single, concise sentence that front-loads the core action and key constraint. There is no filler or redundant information, making it efficient and easy to scan.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a creation tool with no annotations and no output schema, the description is too sparse. It omits important context such as whether the post is immediately published, whether items can mix images and videos, and what response is returned. The 'max 10' is helpful but insufficient for an agent to fully understand the tool's behavior and requirements.

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 coverage is 50% (only 'items' has a description). The tool description adds that carousel supports multiple photos/videos and a max of 10 items, which helps clarify the 'items' parameter. It does not contribute any meaning for 'caption', which lacks schema description, so it only partially compensates.

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 the tool posts a carousel (multiple photos/videos) to Instagram, with a specific verb 'Dang' (post) and resource. It distinguishes itself from sibling tools like post_photo and post_reel by specifying the carousel format.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives such as post_photo or post_reel. It does not mention any exclusions, prerequisites, or comparisons with sibling tools, leaving the agent without decision support.

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

Deploy Server