Skip to main content
Glama
Sign In
instagram-mcp-server

instagram-mcp-server

by qaassimq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Publish Image

instagram_publish_image

Publish a single JPEG image to an Instagram feed using a direct public HTTPS URL, and add captions, alt text, and tags.

Instructions

Publish a single image to the Instagram feed.

The image must be a JPEG served from a public HTTPS URL that returns the file directly — no redirects, no authentication, no HTML wrapper. Meta fetches it server-side, so a local path or a signed URL that expires will fail.

For two or more images in one post use instagram_publish_carousel. For video use instagram_publish_reel.

Example: "post this photo with the caption 'new drop'" -> image_url="https://cdn.example.com/a.jpg", caption="new drop"

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

Input Schema

NameRequiredDescriptionDefault
captionNoCaption text, up to 2200 characters. Hashtags and @mentions work inside the caption. Instagram counts a maximum of 30 hashtags.
alt_textNoAccessibility alt text. Supported on image posts only, not reels or stories.
image_urlYesPublic HTTPS URL of a JPEG image
user_tagsNoPeople to tag. Images need x and y coordinates; videos and reels take username only. The tagged account must be public.
account_idNoInstagram professional account ID. Omit to use the token's own account.
location_idNoFacebook Page ID of a location to tag
collaboratorsNoUp to 3 public usernames invited as collaborators
is_ai_generatedNoMark the content as AI-generated. Set it when the image was AI-created.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly=false, openWorld=true, idempotent=false, destructive=false, so the safety profile is covered. The description adds genuinely non-obvious behavioral context: Meta fetches the image server-side, so local paths, expiring signed URLs, redirects, or auth-protected URLs will silently fail. It omits the publishing quota/rate limit, which the sibling instagram_get_publishing_limit implies 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 short blocks — purpose/sibling routing, the URL constraint that most often causes failures, and a worked example — front-loaded with the verb and zero filler. The example earns its place because it shows how a user phrase decomposes into arguments.

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 an 8-parameter mutation with no output schema, the description covers the highest-risk failure mode (image fetchability) and sibling routing, while the fully-described schema handles per-parameter details. It stops short of noting the account's publishing quota or confirming the post is immediately live, which would round it out.

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; the description earns above that by fleshing out image_url semantics beyond the schema's one-liner (no redirects, no auth, no HTML wrapper, no expiring signed URLs) and by mapping a natural-language request to concrete image_url and caption values in the example.

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 opens with a specific verb and resource ('Publish a single image to the Instagram feed') and immediately names two siblings it is not (carousel for multiple images, reel for video), so an agent can discriminate it without opening any schema.

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 states when to use the alternatives: 'For two or more images in one post use instagram_publish_carousel. For video use instagram_publish_reel.' It also spells out a hard precondition on the image source (direct public HTTPS JPEG, no redirects/auth/HTML wrapper, non-expiring URL).

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