Skip to main content
Glama
exileum

meta-mcp

threads_publish_carousel

Post a carousel of 2-20 images or videos to Threads. Optionally share to Instagram Stories, control who can reply, add captions, topic tags, and quote other posts.

Instructions

Publish a carousel post on Threads with 2-20 images/videos. Supports cross-share to Instagram Stories.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesArray of media items
textNoCaption text
reply_controlNoWho can reply
topic_tagNoTopic tag for the post (1-50 chars, no periods or ampersands)
quote_post_idNoID of a post to quote
share_to_ig_storyNoCross-share this post to linked Instagram as a Story. 'light' = normal, 'dark' = dark mode. Requires threads_share_to_instagram permission and a linked Instagram account. The Threads post still publishes even if cross-share fails.
Behavior3/5

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

No annotations provided, so description is only source. It discloses publish (write) and cross-share behavior, including failure handling for share_to_ig_story. However, lacks details on rate limits, authentication, or other behaviors.

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?

Two sentences, no filler. Front-loaded with key information: publish carousel, item count range, cross-share. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, so return values are unexplained. Tool has 6 parameters and cross-share nuance; description covers core but misses error handling or response format. Could be more comprehensive given complexity.

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 baseline is 3. Description adds minimal extra beyond schema, e.g., cross-share mention. Share_to_ig_story has detailed schema description, so description doesn't need to repeat.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Publish a carousel post on Threads with 2-20 images/videos', specifying verb, resource, and key constraints. It also mentions cross-share to Instagram Stories, distinguishing it from siblings like single image/text posts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description implies usage for carousel posts with 2-20 items and cross-share. No explicit when-not-to-use or alternatives, but the context of siblings makes it clear enough for agent selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/exileum/meta-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server