instagram-mcp-server

Publish Container

instagram_publish_container

Publish a finished Instagram media container to complete an interrupted publish or finalize a carousel. Check container status first to avoid publishing incomplete media.

Instructions

Publish a media container that is already FINISHED.

Use this to complete a publish that was interrupted, or after assembling a carousel with instagram_create_container. Publishing a container that is still IN_PROGRESS fails; check instagram_get_container_status first.

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": {
      "container_id": "<container_id>"
    },
    "name": "instagram_publish_container"
  }
}

Input Schema

Name	Required	Description	Default
`account_id`	No	Instagram professional account ID. Omit to use the token's own account.
`container_id`	Yes	Container ID to publish

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered structurally. The description adds genuinely useful state-machine context: publishing is only valid once the container is FINISHED, and attempting it earlier fails rather than queuing. It stops short of covering re-publish/duplicate behavior (relevant given idempotentHint=false) or any rate limits, leaving a modest gap.

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 short paragraphs, front-loaded with the action and then the routing/precondition detail. Every sentence carries information the agent needs, and the capitalized state markers (FINISHED, IN_PROGRESS) make the precondition scannable.

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?

There is no output schema, so the description is the only place return semantics could live, and it says nothing about what a successful publish yields (media ID, permalink) or that the result is a live post. Preconditions and alternatives are otherwise complete for a two-parameter tool, so this is a small but real gap.

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 100% for both parameters, including the 'omit to use the token's own account' default for account_id, so the schema does the heavy lifting. The description adds only indirect meaning by tying the call to container FINISHED state, without saying anything about container ID origin or the optional account override. Baseline 3 applies.

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 first sentence gives a specific verb and resource ('Publish a media container') plus a hard precondition ('already FINISHED'), which an agent cannot get from the name alone. The second paragraph further separates this tool from instagram_create_container (assembly) and instagram_get_container_status (pre-check), so sibling selection is unambiguous.

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

Usage Guidelines5/5

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

It explicitly names both when to use it ('complete a publish that was interrupted, or after assembling a carousel') and when it will fail ('Publishing a container that is still IN_PROGRESS fails'). It also names the prerequisite tool to call first ('check instagram_get_container_status first'), which is the exact routing decision an agent needs.

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

Deploy Server