Skip to main content
Glama
mikusnuz

meta-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ig_publish_video

Publishes a standalone video as an Instagram Reel and shares it to the feed, waiting for processing to finish before posting.

Instructions

Publish a standalone video as a Reel and share it to the feed. Waits for video processing before publishing.

Input Schema

NameRequiredDescriptionDefault
captionNoPost caption
video_urlYesPublic HTTPS URL of the video
location_idNoFacebook Page location ID
thumb_offsetNoThumbnail offset in ms
trial_paramsNoPublish as a Trial Reel; graduate manually or automatically based on performance
is_ai_generatedNoApply the AI info label to the published media
is_paid_partnershipNoApply the Paid partnership label
branded_content_sponsor_idsNoInstagram user IDs of up to two brand partners

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.2.2
    • addedInput schema / properties / branded_content_sponsor_ids
      Added value: +{
+  "description": "Instagram user IDs of up to two brand partners",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 2,
+  "type": "array"
+}
    • addedInput schema / properties / is_ai_generated
      Added value: +{
+  "description": "Apply the AI info label to the published media",
+  "type": "boolean"
+}
    • addedInput schema / properties / is_paid_partnership
      Added value: +{
+  "description": "Apply the Paid partnership label",
+  "type": "boolean"
+}
    • addedInput schema / properties / trial_params
      Added value: +{
+  "additionalProperties": false,
+  "description": "Publish as a Trial Reel; graduate manually or automatically based on performance",
+  "properties": {
+    "graduation_strategy": {
+      "enum": [
+        "MANUAL",
+        "SS_PERFORMANCE"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "graduation_strategy"
+  ],
+  "type": "object"
+}
  2. First observedv2.0.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, but it does add one important trait: it waits for video processing before publishing. It still does not disclose permissions, rate limits, failure behavior, or what result is returned after the publish action.

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 two sentences with no wasted text. The core action and the processing-wait behavior are front-loaded and easy to scan.

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 publishing mutation with no annotations and no output schema, the description is too thin. It covers the basic action and the processing wait but omits sibling differentiation, permission requirements, and any indication of the returned result or failure state.

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%, so all parameters including video_url, caption, trial_params, and branded content fields are already documented in the schema. The description adds no parameter-level semantics beyond that baseline.

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 states a specific verb and resource: publish a standalone video as a Reel and share it to the feed. However, it does not distinguish this tool from the sibling ig_publish_reel, and calling the output a Reel makes the overlap even less clear.

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 use this tool instead of ig_publish_reel, ig_publish_story, or ig_publish_carousel. It also omits prerequisites such as account permissions or whether a container must already exist.

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