meta-social-mcp

ig_publish_carousel

Publish multi-image carousel posts to Instagram with 2-10 images and an optional caption via the Meta Graph API.

Instructions

Publish a multi-image carousel post (2-10 images) to 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": {
      "image_urls": "<image_urls>"
    },
    "name": "ig_publish_carousel"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 8, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only restates that the tool 'publishes', which implies a side-effectful action, but it does not mention authentication requirements, error behavior, whether existing posts get replaced, or any other behavioral traits. This is a significant gap for a write operation.

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 sentence with no filler or redundant information. It is front-loaded with the core purpose and key constraint. Every word contributes value.

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?

For a tool with only two parameters and no output schema, the description gives the essential action and the image-count constraint. However, with no annotations, it lacks crucial context such as expected media URL formats, side effects, or any preconditions. It is minimally adequate but not complete.

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%, yet the description provides no extra meaning for the parameters. It mentions '2-10 images', which merely echoes the minItems/maxItems constraints already present in the schema, and it does not describe the caption parameter at all. The agent must infer caption's purpose from the property name alone.

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 uses a specific verb ('publish'), a clear resource ('multi-image carousel post'), and target platform ('Instagram'). The '2-10 images' detail distinguishes it from single-image or video publishing siblings like ig_publish_photo and ig_publish_video.

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 description implies its usage: you use this when publishing a carousel with multiple images. However, it provides no explicit guidance on when not to use it or which sibling tool would be more appropriate for other post types. Usage is understandable but not actively guided.

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