meta-mcp

threads_publish_carousel

Publish a Threads carousel post with 2–20 images or videos, caption, topic tag, reply controls, and optional Instagram cross-sharing.

Instructions

Publish a carousel post on Threads with 2-20 images/videos.

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": "threads_publish_carousel"
  }
}

Input Schema

Name	Required	Description
`text`	No	Caption text
`items`	Yes	Array of media items
`topic_tag`	No	Topic tag for the post
`location_id`	No	Location ID to tag (from threads_search_locations)
`quote_post_id`	No	ID of a post to quote
`reply_control`	No	Who can reply
`crossreshare_to_ig`	No	Also share this post to the user's linked Instagram account as a Story
`enable_reply_approvals`	No	Require replies to be approved before they're published
`crossreshare_to_ig_dark_mode`	No	Cross-share to Instagram Stories in dark mode

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.2.2Oct 26, 2026

addedInput schema / properties / crossreshare_to_ig

Added value: +{
+  "description": "Also share this post to the user's linked Instagram account as a Story",
+  "type": "boolean"
+}

addedInput schema / properties / crossreshare_to_ig_dark_mode

Added value: +{
+  "description": "Cross-share to Instagram Stories in dark mode",
+  "type": "boolean"
+}

addedInput schema / properties / enable_reply_approvals

Added value: +{
+  "description": "Require replies to be approved before they're published",
+  "type": "boolean"
+}

addedInput schema / properties / location_id

Added value: +{
+  "description": "Location ID to tag (from threads_search_locations)",
+  "type": "string"
+}

First observedv2.0.1Mar 19, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations, so the description carries the full burden, yet it only restates the item count. It says nothing about the publish being irreversible, that media URLs must be public HTTPS, how partial failures behave, or rate limits — all material for a write operation on 9 parameters.

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?

A single front-loaded sentence with no filler. It is tight, though the brevity comes at the cost of the behavioral and usage detail noted above rather than from disciplined editing.

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 9-parameter publishing mutation with no annotations and no output schema needs far more than one sentence: it should cover return value (a post/container ID), whether publishing is async, and cross-share implications. None of that context exists.

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 every parameter including reply_control, crossreshare_to_ig and quote_post_id is already documented in structure. The description's '2-20 images/videos' simply restates minItems/maxItems, adding no new parameter meaning, so the baseline 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 and resource ('Publish a carousel post on Threads') plus the 2-20 media constraint, which separates it from threads_publish_text, threads_publish_image and threads_publish_video. It does not explicitly name those siblings, but the carousel scope is unambiguous.

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 a carousel rather than a single image/video post, no prerequisites (media must be at URL-accessible, auth required), and no mention that container status may need to be polled via threads_get_container_status. Usage must be inferred entirely 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