Skip to main content
Glama
Sign In
meta-mcp

meta-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ig_publish_carousel

Publish an Instagram carousel post with 2-10 images or videos, including optional captions, alt text, location, and partnership labels.

Instructions

Publish a carousel (album) post with 2-10 images/videos. Each item needs an image_url or video_url.

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": {
      "items": "<items>"
    },
    "name": "ig_publish_carousel"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesArray of media items
captionNoPost caption
location_idNoFacebook Page location ID
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. Changed3 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"
+}
  2. First observedv2.0.1

TDQS

C2.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 the full disclosure burden, yet it says nothing about publishing being public and effectively irreversible, no mention of required account permissions or rate limits, and no mention of the container/polling flow that Instagram publishing usually requires. Only the item count constraint 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.

Conciseness4/5

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

Two sentences, front-loaded with the action and the key constraint, with no filler. The brevity is undermined only by the inaccurate field names in the second sentence.

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?

A six-parameter publishing tool with no annotations and no output schema needs the description to cover return values (e.g. resulting media ID), failure modes, and the async container flow. None of that appears; caption limits, alt_text, location, and branded-content constraints are left entirely to the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description actively misnames the parameter: it says each item needs an 'image_url or video_url' while the schema defines a single 'url' field plus a 'type' enum. An agent following the description literally would send fields that fail additionalProperties:false.

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 and resource ('Publish a carousel (album) post') and names the cardinality constraint, which clearly separates it from ig_publish_photo, ig_publish_video and ig_publish_reel. The sibling it most resembles, threads_publish_carousel, is not distinguished, but the platform prefix makes that implicit.

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 choose this over ig_publish_photo (single image) or threads_publish_carousel, and no exclusions or prerequisites. The 2-10 item bound is the only implicit selector, so an agent must infer the rest from the tool name.

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