Skip to main content
Glama
Instagram Campaign MCP

Instagram Campaign MCP

by enimarix

publish_carousel

Publish a 2–10 slide Instagram carousel with image or video items, an optional caption, and campaign metadata, while all slides are cropped to the first slide's ratio.

Instructions

Publish a carousel now. items: 2-10 of {"image_url": ...} or {"video_url": ...} (optional "alt_text" on images). Images must be JPEG. All slides are cropped to the first slide's ratio (4:5 to 1.91:1).

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

Input Schema

NameRequiredDescriptionDefault
itemsYes
captionNo
variantNo
campaignNo
hypothesisNo
location_idNo
collaboratorsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, openWorldHint=true, destructiveHint=false, idempotentHint=false), so the bar is lower. The description still adds genuinely useful behavior: publication is immediate, and all slides get cropped to the first slide's aspect ratio, which is a non-obvious side effect an agent could not infer from structured fields.

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

Conciseness4/5

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

The action is front-loaded in the first clause, followed by the constraints an agent needs before constructing a call. Three dense sentences with no filler; only the parenthetical alt_text note interrupts the flow slightly.

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 values need not be described. However, for a 7-parameter publishing tool with 0% schema coverage, the description leaves most parameters and any rate-limit or permission context unaddressed, which is a meaningful gap for a non-idempotent write operation.

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% across 7 parameters, so the description carries the full burden. It explains the required `items` parameter well (count bounds, accepted key shapes, alt_text only on images), but caption, variant, campaign, hypothesis, location_id, and collaborators receive no explanation at all, including the ambiguous analytics-style fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource, "Publish a carousel now," which is clearly distinct from the image/reel/story siblings, and "now" implicitly contrasts with scheduling tools. It stops short of explicitly naming an alternative, so the differentiation is inferred rather than stated.

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?

Usage is implied by the operational constraints (2-10 slides, JPEG images, first-slide ratio cropping) rather than stated as when-to-use guidance. There is no explicit statement of when to choose this over schedule_post or publish_image, and no prerequisites such as required permissions or account type.

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