Skip to main content
Glama
inyogeshwar

Meta Social Technologies MCP Server

by inyogeshwar

publish_instagram_reel

Publishes an Instagram Reel to an account from a direct public MP4 URL, adding an optional caption and hashtags.

Instructions

Publish a video reel with caption to Instagram account in.yogeshwar.

Input Schema

NameRequiredDescriptionDefault
captionNoCaption and hashtags for the reel.
video_urlYesDirect public URL of the MP4 video file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It implies a write operation but says nothing about permissions needed, whether publishing is immediate and public, rate limits, or container-processing delays typical of Instagram reels. Only the hard-coded target account is disclosed.

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?

A single sentence with the action verb front-loaded and zero redundant wording. Nothing needs to be trimmed.

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?

For a mutation tool with no annotations and no output schema, the description omits what an agent needs: confirmations that the post is public, the expected outcome (e.g., a media ID), and any failure or throttling behavior. The 2 well-documented parameters keep it from being worse.

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%, with both video_url (direct public MP4 URL) and caption (caption and hashtags) already documented in the schema. The description adds only that caption accompanies a video reel, so the baseline of 3 applies.

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?

States a specific verb (publish) and a specific resource (video reel) with an explicit target account. The word 'reel' plus 'video' distinguishes it from publish_instagram_photo and the facebook/threads publish siblings, though no sibling is named directly.

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?

There is no guidance on when to choose this over publish_instagram_photo or the other publish_* tools, and no prerequisites such as account permissions or video format requirements are mentioned. Usage must be inferred entirely from the name.

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