Enterprise Threads MCP Server

create_carousel_post

Create carousel posts on Threads with 2-20 images or videos, captions, alt text, and aspect ratio settings for professional engagement.

Instructions

Create multi-media carousel posts with up to 20 items (September 2024 update)

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": {
      "media_urls": "<media_urls>",
      "text": "<text>"
    },
    "name": "create_carousel_post"
  }
}

Input Schema

Name	Required	Description
`text`	Yes	Post caption text
`alt_texts`	No	Alt text for each media item (accessibility)
`media_urls`	Yes	Array of image/video URLs for carousel (2-20 items supported)
`carousel_settings`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv5.1.0Aug 14, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only mentions the 20-item limit and the September 2024 update, but does not disclose side effects (e.g., publishing to profile), required permissions, or error behavior. This is minimal coverage for a creation tool.

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 a single, front-loaded sentence ('Create multi-media carousel posts with up to 20 items') that is immediately understandable. The parenthetical '(September 2024 update)' is somewhat extraneous but provides useful temporal context, so it earns its place.

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 tool with no annotations and no output schema, the description is too sparse. It does not explain the outcome (e.g., post ID returned), whether the post is published immediately or saved as a draft, or how carousel_settings affect the behavior. Sibling tools like schedule_post and create_post_with_restrictions suggest alternative workflows that are not addressed.

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?

The input schema already provides descriptions for all parameters (75%+ coverage), so the baseline is 3. The description adds marginal value by highlighting the 20-item limit and the September 2024 update, which reinforces media_urls maxItems, but it does not clarify semantics beyond the schema.

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 action ('Create multi-media carousel posts') and resource, and adds a key constraint ('up to 20 items'). However, it does not explicitly differentiate from other creation tools like create_post_with_restrictions or schedule_post, which also create posts.

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 is provided on when to use this tool versus alternatives. The description does not mention prerequisites, such as whether media must be hosted elsewhere or whether the post publishes immediately. The presence of several sibling creation-related tools makes this lack of guidance a significant gap.

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

Deploy Server