Instagram Control MCP Server

instagram_post_reel

Post an Instagram Reel with full caption control to increase organic reach. Customize hashtags, mentions, location, and comment settings.

Instructions

Post a Reel with full caption control. Reels have the highest organic reach.

Parameters:

video_path_or_url: Local path or URL to MP4 video
caption: Caption text
hashtags: Comma-separated hashtags (crucial for Reel discovery)
mentions: Comma-separated @mentions
location_name: Location tag
disable_comments: Set True to disable comments

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": {
      "video_path_or_url": "<video_path_or_url>",
      "caption": "<caption>"
    },
    "name": "instagram_post_reel"
  }
}

Input Schema

Name	Required	Description	Default
`video_path_or_url`	Yes
`caption`	Yes
`hashtags`	No
`mentions`	No
`location_name`	No
`disable_comments`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 20, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action (post) but does not disclose behavioral traits such as login requirements, rate limits, or what happens on success/failure. It lacks details about side effects or constraints.

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?

The description is extremely concise: a single sentence followed by a parameter list. Every sentence and line adds value without redundancy. The structure is front-loaded with the main purpose and then details.

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?

Given an output schema exists (not shown), the description doesn't need to explain return values. However, it lacks completeness in areas like prerequisites (e.g., must be logged in) and behavioral context (e.g., whether it overwrites or creates). With no annotations, it could do more to define the tool's complete behavior.

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?

With 0% schema description coverage, the description compensates well by explaining each parameter's purpose and format (e.g., 'Local path or URL to MP4 video', 'Comma-separated hashtags (crucial for Reel discovery)'). This adds meaningful context beyond the schema's type definitions.

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 clearly states 'Post a Reel', a specific action on a specific resource. It mentions 'full caption control' and the benefit of highest organic reach, which distinguishes it from sibling tools like instagram_post_photo or instagram_post_video.

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 description mentions that Reels have the highest organic reach, implying a benefit, but does not provide explicit guidance on when to use this tool versus alternatives like instagram_post_video or instagram_post_photo. No exclusions or prerequisites are stated.

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

Deploy Server