Skip to main content
Glama
Sign In
Instagram Account MCP

Instagram Account MCP

by joinhackyard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Publish a carousel

publish_carousel

Publish or schedule Instagram carousels of 2–20 images and videos, with per-slide alt text, user tags and fit control to fix cropping. Requires user confirmation.

Instructions

Publish (or schedule) a carousel of 2 to 20 images and/or videos (videos 3-60 s). Instagram crops every item to the first item's shape; use fit to control reframing. Alt text and user tags per image. Needs the user's confirmation; runs in the background.

Input Schema

NameRequiredDescriptionDefault
fitNoReframing when converting: keep (only clamp into the allowed range), crop (fill the frame from the centre) or blur (whole frame over a blurred fill). Reels/stories target 9:16.
itemsYesThe slides, in order.
accountNoWhich connected account: @username or Instagram user ID. Omit to use the default account.
captionNoCaption (max 2,200 characters, 30 hashtags, 20 @mentions). The first ~125 characters show before 'more'. Captions can't be edited through the API after publishing.
prepareNoConvert to Instagram's specs with ffmpeg first (JPEG, H.264/AAC MP4, allowed aspect ratio and length). Default true.
templateNoTemplate from list_templates: adds header/footer, hashtags, first comment, collaborators.
publish_atNoSchedule: ISO 8601 date-time with timezone, at least 10 minutes and at most 75 days ahead. Instagram has no API scheduling, so this computer (or the background service) publishes it then; if the computer is off and the time passes by more than 2 hours, it is not published late (reschedule or resume_publish).
location_idNoFacebook Page ID of a place (see find_location).
wait_secondsNoWait this long for publishing before returning; then follow get_publish_status.
collaboratorsNoUp to 3 usernames invited as collaborators (they must accept in the app).
first_commentNoPosted as the first comment right after publishing (hashtags, credits, links).
is_ai_generatedNoSelf-disclose that the content was made or edited with AI (shows an AI label).
confirmation_tokenNoOnly after the user approved: the confirmation_token returned by the previous call with identical arguments.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses that the user's confirmation is required, that execution runs in the background, that Instagram crops every item to the first item's shape, and the scheduling caveat that a missed window more than 2 hours late is not published (reschedule or resume_publish). These are exactly the operational traits an agent needs before invoking a non-idempotent, open-world write.

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?

Four short sentences, front-loaded with the action and limits, then the cropping behavior, then the per-item extras, then the confirmation/background caveat. No filler.

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?

For a 13-parameter mutation with no output schema, the description covers the risky parts (confirmation, background execution, scheduling failure mode, immutability of captions after publish). Minor gaps remain around the return value and the wait_seconds/get_publish_status handoff, though the schema documents those.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains why 'fit' matters (Instagram crops to the first item's shape) and that alt text and user tags are per image, which the schema alone does not motivate.

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?

States a specific verb and resource ('Publish (or schedule) a carousel') plus the cardinality constraint (2 to 20 images/videos, videos 3-60 s), which cleanly separates it from publish_photo, publish_reel and publish_story in the sibling list.

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

Usage Guidelines4/5

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

Makes clear this is the multi-item path and that it can either publish now or schedule, and flags the confirmation prerequisite. It does not explicitly name the sibling tools to use instead for single photos or reels, so routing is inferred from the carousel scope rather than stated.

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

Deploy Server

Other Tools