Skip to main content
Glama
Instagram Campaign MCP

Instagram Campaign MCP

by enimarix

publish_image

Publish a single-image Instagram feed post now from a public HTTPS JPEG. Store campaign, variant, and hypothesis locally for A/B comparison.

Instructions

Publish a single-image feed post now. Image must be a public HTTPS JPEG (Instagram's API does not take PNG) with an aspect ratio between 4:5 and 1.91:1. campaign/variant/hypothesis are stored locally for A/B comparison.

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_url": "<image_url>"
    },
    "name": "publish_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
captionNo
variantNo
alt_textNo
campaignNo
image_urlYes
hypothesisNo
location_idNo
collaboratorsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4/5.0
Behavior4/5

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

The annotations only say this is a non-read-only, open-world, non-idempotent, non-destructive write. The description adds hard external constraints: a public HTTPS URL, JPEG only (no PNG), and an aspect ratio window of 4:5 to 1.91:1. It does not say the post goes live immediately and cannot be undone, or mention publishing rate limits even though a get_publishing_limit sibling exists.

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?

Three dense sentences, front-loaded with the action, then validation constraints, then the non-obvious local-only bookkeeping fields. No filler or restated name.

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?

With an output schema present, the description does not need to explain return values, and it covers the highest-risk input (image_url) plus the confusing A/B fields. The remaining gap is the everyday parameters (caption, alt_text, collaborators, location_id), whose names are largely self-explanatory, so the omission is minor rather than crippling.

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 0% across 8 parameters, so the description has to carry the load and only partly does. It documents image_url's format requirements and explains that campaign/variant/hypothesis are stored locally for A/B comparison. caption, alt_text, location_id, and collaborators are left completely undefined in both the schema and the description.

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 states a specific verb ('Publish') and resource ('a single-image feed post now'), which distinguishes it from the carousel, reel, and story publishing siblings without having to name them. An agent can pick the right publisher from the description alone.

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?

'now' implies immediacy and implicitly contrasts with the scheduling siblings, but the description never states when to choose schedule_post or reschedule_post instead. Usage is implied rather than spelled out, and no exclusions or prerequisites are given.

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