Skip to main content
Glama
Instagram Campaign MCP

Instagram Campaign MCP

by enimarix

publish_story

Publish an Instagram Story now using exactly one image or video URL in 9:16 format; bake stickers, links, or text overlays into the media since the API cannot add them.

Instructions

Publish a Story now (exactly one of image_url / video_url, 9:16; images JPEG). The API cannot add stickers, links or text overlays: bake them into the media.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "publish_story"
  }
}

Input Schema

NameRequiredDescriptionDefault
variantNo
campaignNo
image_urlNo
video_urlNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already disclose a non-read-only, non-idempotent, open-world write, so the description is not carrying the full burden. It nonetheless adds real behavioral value the annotations cannot: the mutually exclusive media input, the 9:16 JPEG requirement, and the API limitation that overlays must be baked into the media rather than added server-side.

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?

Two sentences, zero filler, and the action plus hardest constraint (exactly one media URL) is front-loaded before the format detail and the overlay caveat. Every clause carries information an agent would otherwise have to guess.

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, and the media constraints are well covered. The gaps are the undocumented variant/campaign parameters and the absence of any routing guidance among the four sibling publish tools, which matters for a tool whose wrong selection is costly.

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, and it does for the two media parameters by defining the exactly-one-of rule plus format constraints. However, 'variant' and 'campaign' — half the parameters — receive no explanation at all, leaving the compensation incomplete.

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?

"Publish a Story now" names a specific verb and a distinct resource (Story), which separates it from publish_image/publish_reel/publish_carousel by format, and the parenthetical adds the media constraints. It stops short of explicitly stating that feed images go to publish_image, so the sibling split is implied 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?

The word "now" implies immediate publishing as opposed to schedule_post, but the description never states when a Story is the correct format instead of a Reel, image, or carousel, and never mentions prerequisites such as account permissions. Usage is inferable, not guided.

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