Skip to main content
Glama
exileum

meta-mcp

ig_publish_reel

Publish an Instagram Reel from a public video URL, with options for caption, cover image, collaborators, and feed sharing. Waits for video processing to complete.

Instructions

Publish a Reel (short video). Waits for video processing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
captionNoReel caption (max 2200 chars)
cover_urlNoCustom cover image HTTPS URL
video_urlYesPublic HTTPS URL of the video
thumb_offsetNoThumbnail offset in ms
collaboratorsNoOptional. Up to 3 unique Instagram usernames to invite as collaborators. Per Instagram Graph API: supported for Feed image, Reels, and Carousels — not supported for Stories. Leading '@' characters and surrounding whitespace are auto-stripped before the uniqueness check.
share_to_feedNoAlso share to feed (default true)
Behavior3/5

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

The description adds that it 'waits for video processing', a useful behavioral detail beyond annotations. However, it does not disclose post-processing effects like feed sharing default (share_to_feed defaults true), rate limits, or auth requirements. Annotations indicate a write operation but no destructive hint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise (two sentences, 10 words) and front-loaded with the main action. It could be slightly improved by clarifying the output or context, but it is not verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema is provided, and the description does not mention what the tool returns (e.g., container ID, status). Given the complexity of publishing a reel, more information about the result or processing time would be helpful.

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 100%, so the input schema already describes all parameters. The description adds no additional meaning to any parameter, so it meets the baseline but does not exceed it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool publishes a Reel (short video) and mentions waiting for processing. It distinguishes from siblings like ig_publish_video by specifying 'short video', but could be more explicit about its unique role.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives such as ig_publish_video or ig_publish_story. No mention of prerequisites or best practices.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/exileum/meta-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server